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

城市(city): Phoenix

省份(region): Arizona

国家(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.160.0.0 - 20.175.255.255
CIDR:           20.160.0.0/12
NetName:        MSFT
NetHandle:      NET-20-160-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-02-22
Updated:        2017-02-22
Ref:            https://rdap.arin.net/registry/ip/20.160.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: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

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: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-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

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


#
# 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.168.120.250
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11887
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.168.120.250.			IN	A

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

;; Query time: 31 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 27 05:00:26 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
250.120.168.20.in-addr.arpa domain name pointer azpdwg3cm3eh.stretchoid.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
250.120.168.20.in-addr.arpa	name = azpdwg3cm3eh.stretchoid.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
119.207.126.21 attackspam
Dec  2 18:26:03 ny01 sshd[11611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.207.126.21
Dec  2 18:26:05 ny01 sshd[11611]: Failed password for invalid user hamza from 119.207.126.21 port 38174 ssh2
Dec  2 18:33:11 ny01 sshd[12569]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.207.126.21
2019-12-03 07:36:48
198.211.110.133 attackspam
Dec  3 02:54:02 server sshd\[17029\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.110.133  user=root
Dec  3 02:54:04 server sshd\[17029\]: Failed password for root from 198.211.110.133 port 44850 ssh2
Dec  3 02:59:52 server sshd\[18501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.110.133  user=root
Dec  3 02:59:54 server sshd\[18501\]: Failed password for root from 198.211.110.133 port 59488 ssh2
Dec  3 03:04:50 server sshd\[21127\]: Invalid user ruma from 198.211.110.133
Dec  3 03:04:50 server sshd\[21127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.110.133 
...
2019-12-03 08:10:33
124.156.117.111 attack
Dec  3 00:01:19 OPSO sshd\[14613\]: Invalid user uno50 from 124.156.117.111 port 46560
Dec  3 00:01:19 OPSO sshd\[14613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.156.117.111
Dec  3 00:01:21 OPSO sshd\[14613\]: Failed password for invalid user uno50 from 124.156.117.111 port 46560 ssh2
Dec  3 00:07:34 OPSO sshd\[16218\]: Invalid user safholm from 124.156.117.111 port 57476
Dec  3 00:07:34 OPSO sshd\[16218\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.156.117.111
2019-12-03 07:51:07
139.59.61.134 attackspam
Dec  2 20:45:39 XXX sshd[11733]: Invalid user kilsaas from 139.59.61.134 port 54401
2019-12-03 08:00:29
51.38.98.23 attackspam
Dec  2 23:28:03 hcbbdb sshd\[10006\]: Invalid user zitko from 51.38.98.23
Dec  2 23:28:03 hcbbdb sshd\[10006\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.ip-51-38-98.eu
Dec  2 23:28:06 hcbbdb sshd\[10006\]: Failed password for invalid user zitko from 51.38.98.23 port 45454 ssh2
Dec  2 23:33:17 hcbbdb sshd\[10650\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.ip-51-38-98.eu  user=lp
Dec  2 23:33:19 hcbbdb sshd\[10650\]: Failed password for lp from 51.38.98.23 port 56490 ssh2
2019-12-03 07:45:59
13.69.31.111 attackbotsspam
RDP Bruteforce
2019-12-03 07:51:35
103.28.2.60 attack
Dec  3 00:34:15 localhost sshd\[11079\]: Invalid user home from 103.28.2.60 port 51696
Dec  3 00:34:15 localhost sshd\[11079\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.28.2.60
Dec  3 00:34:18 localhost sshd\[11079\]: Failed password for invalid user home from 103.28.2.60 port 51696 ssh2
2019-12-03 07:42:54
45.148.10.62 attackspambots
SASL PLAIN auth failed: ruser=...
2019-12-03 07:44:51
195.58.123.109 attack
2019-12-02T21:33:36.423466abusebot-5.cloudsearch.cf sshd\[1420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host.195.58.123.109.bitcom.se  user=adm
2019-12-03 07:46:19
62.162.103.206 attack
Wordpress Attacks [Scanning for wp-login.php] @ 2019-12-02 23:12:40
2019-12-03 07:58:46
222.180.162.8 attackspambots
Dec  3 00:17:52 server sshd\[6945\]: Invalid user host from 222.180.162.8
Dec  3 00:17:52 server sshd\[6945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.180.162.8 
Dec  3 00:17:54 server sshd\[6945\]: Failed password for invalid user host from 222.180.162.8 port 37514 ssh2
Dec  3 00:33:24 server sshd\[11553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.180.162.8  user=root
Dec  3 00:33:26 server sshd\[11553\]: Failed password for root from 222.180.162.8 port 58053 ssh2
...
2019-12-03 07:52:29
51.77.192.141 attackspambots
Dec  3 00:07:54 localhost sshd\[7605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.192.141  user=root
Dec  3 00:07:55 localhost sshd\[7605\]: Failed password for root from 51.77.192.141 port 47158 ssh2
Dec  3 00:13:14 localhost sshd\[8175\]: Invalid user deng from 51.77.192.141 port 58504
2019-12-03 07:32:53
39.88.108.42 attack
Port scan on 2 port(s): 1433 3389
2019-12-03 07:56:48
157.245.74.137 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2019-12-03 07:54:34
23.254.229.232 attackspam
Dec  3 00:14:51 lnxded63 sshd[5733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.254.229.232
Dec  3 00:14:51 lnxded63 sshd[5733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.254.229.232
2019-12-03 07:52:51

最近上报的IP列表

204.236.211.208 2606:4700:10::6816:4702 2606:4700:10::6814:6061 2606:4700:10::6814:7224
223.123.44.122 67.205.159.220 1.14.110.85 52.28.16.197
143.244.144.178 121.230.89.109 171.67.71.223 64.62.156.218
64.62.156.216 217.154.93.126 2606:4700:10::6814:7822 48.214.144.160
35.93.224.196 120.79.84.40 38.84.202.52 107.170.53.181