必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): San Antonio

省份(region): Texas

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       20.33.0.0 - 20.128.255.255
CIDR:           20.128.0.0/16, 20.36.0.0/14, 20.48.0.0/12, 20.40.0.0/13, 20.34.0.0/15, 20.33.0.0/16, 20.64.0.0/10
NetName:        MSFT
NetHandle:      NET-20-33-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-10-18
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/20.33.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-ARIN

OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 20.65.219.65
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28989
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.219.65.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026083001 1800 900 604800 86400

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 31 08:01:12 CST 2026
;; MSG SIZE  rcvd: 105
HOST信息:
Host 65.219.65.20.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 65.219.65.20.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
76.102.119.124 attack
SASL PLAIN auth failed: ruser=...
2020-02-08 09:15:49
223.26.48.64 attackbots
27017/tcp 7443/tcp 8443/tcp...
[2020-01-08/02-07]10pkt,5pt.(tcp)
2020-02-08 08:43:20
139.162.197.24 attackbotsspam
33848/udp 33848/udp 33848/udp
[2020-02-05/07]3pkt
2020-02-08 08:47:23
176.18.165.16 attackbotsspam
Email rejected due to spam filtering
2020-02-08 08:46:13
183.158.9.37 attackbotsspam
port 23
2020-02-08 08:45:11
222.186.173.183 attackspam
Feb  8 01:51:29 jane sshd[13323]: Failed password for root from 222.186.173.183 port 64640 ssh2
Feb  8 01:51:33 jane sshd[13323]: Failed password for root from 222.186.173.183 port 64640 ssh2
...
2020-02-08 09:06:52
185.175.93.14 attack
02/07/2020-20:11:52.376319 185.175.93.14 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-02-08 09:16:31
144.217.83.201 attack
Feb  7 23:37:49 tuxlinux sshd[44778]: Invalid user xea from 144.217.83.201 port 39748
Feb  7 23:37:49 tuxlinux sshd[44778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.83.201 
Feb  7 23:37:49 tuxlinux sshd[44778]: Invalid user xea from 144.217.83.201 port 39748
Feb  7 23:37:49 tuxlinux sshd[44778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.83.201 
Feb  7 23:37:49 tuxlinux sshd[44778]: Invalid user xea from 144.217.83.201 port 39748
Feb  7 23:37:49 tuxlinux sshd[44778]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.83.201 
Feb  7 23:37:52 tuxlinux sshd[44778]: Failed password for invalid user xea from 144.217.83.201 port 39748 ssh2
...
2020-02-08 08:38:02
178.46.215.45 attackspam
23/tcp 23/tcp 23/tcp...
[2020-02-06/07]11pkt,1pt.(tcp)
2020-02-08 09:00:18
51.83.41.120 attackbots
Feb  7 23:37:29 cp sshd[18281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.41.120
2020-02-08 08:58:19
31.13.131.148 attack
2020-02-07T19:31:26.7528501495-001 sshd[29089]: Invalid user kmd from 31.13.131.148 port 51256
2020-02-07T19:31:26.7614221495-001 sshd[29089]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.13.131.148
2020-02-07T19:31:26.7528501495-001 sshd[29089]: Invalid user kmd from 31.13.131.148 port 51256
2020-02-07T19:31:28.8292471495-001 sshd[29089]: Failed password for invalid user kmd from 31.13.131.148 port 51256 ssh2
2020-02-07T19:33:43.7399011495-001 sshd[29269]: Invalid user via from 31.13.131.148 port 43344
2020-02-07T19:33:43.7477101495-001 sshd[29269]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.13.131.148
2020-02-07T19:33:43.7399011495-001 sshd[29269]: Invalid user via from 31.13.131.148 port 43344
2020-02-07T19:33:45.9559001495-001 sshd[29269]: Failed password for invalid user via from 31.13.131.148 port 43344 ssh2
2020-02-07T19:36:00.2287421495-001 sshd[29444]: Invalid user uyu from 31.13.131.
...
2020-02-08 08:59:33
58.255.7.117 attack
badbot
2020-02-08 09:07:14
45.143.222.112 attackspambots
Unauthorized connection attempt from IP address 45.143.222.112 on Port 25(SMTP)
2020-02-08 09:01:40
171.221.236.56 attackspam
23/tcp
[2020-02-07]1pkt
2020-02-08 09:19:24
171.251.49.210 attack
139/tcp 445/tcp
[2020-02-05]2pkt
2020-02-08 08:51:07

最近上报的IP列表

36.143.128.172 183.199.243.246 183.198.102.214 112.37.250.14
112.22.225.146 34.48.243.130 35.203.211.189 58.255.237.54
42.239.54.107 42.236.217.217 39.171.148.234 39.162.168.34
36.143.96.152 183.251.169.151 182.121.164.8 14.1.105.113
1.27.48.208 119.187.26.31 116.113.168.131 115.56.119.170