必须是合法有效的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

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

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: 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


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

;; QUESTION SECTION:
;20.169.106.57.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 21 17:01:11 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
57.106.169.20.in-addr.arpa domain name pointer azpdwgb506wl.stretchoid.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
57.106.169.20.in-addr.arpa	name = azpdwgb506wl.stretchoid.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
108.190.190.48 attackspam
Failed password for invalid user user3 from 108.190.190.48 port 53238 ssh2
2020-09-04 15:09:00
123.171.42.28 attack
Lines containing failures of 123.171.42.28
Sep  2 04:12:33 newdogma sshd[22349]: Connection closed by 123.171.42.28 port 55930 [preauth]
Sep  2 04:14:17 newdogma sshd[22639]: Invalid user mysql from 123.171.42.28 port 47770
Sep  2 04:14:17 newdogma sshd[22639]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.171.42.28 
Sep  2 04:14:19 newdogma sshd[22639]: Failed password for invalid user mysql from 123.171.42.28 port 47770 ssh2
Sep  2 04:14:21 newdogma sshd[22639]: Received disconnect from 123.171.42.28 port 47770:11: Bye Bye [preauth]
Sep  2 04:14:21 newdogma sshd[22639]: Disconnected from invalid user mysql 123.171.42.28 port 47770 [preauth]
Sep  2 04:16:08 newdogma sshd[23038]: Invalid user stack from 123.171.42.28 port 39616
Sep  2 04:16:08 newdogma sshd[23038]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.171.42.28 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip
2020-09-04 14:32:57
138.197.130.138 attackspambots
2020-09-04T08:17:48+0200 Failed SSH Authentication/Brute Force Attack. (Server 9)
2020-09-04 14:47:52
115.73.247.7 attack
Automatic report - Port Scan Attack
2020-09-04 14:44:50
106.12.26.160 attackbots
Sep  4 05:56:52 prod4 sshd\[24704\]: Invalid user test from 106.12.26.160
Sep  4 05:56:54 prod4 sshd\[24704\]: Failed password for invalid user test from 106.12.26.160 port 36572 ssh2
Sep  4 06:04:40 prod4 sshd\[27383\]: Failed password for root from 106.12.26.160 port 53720 ssh2
...
2020-09-04 14:54:33
186.22.74.193 attack
Sep  3 18:48:08 mellenthin postfix/smtpd[19006]: NOQUEUE: reject: RCPT from unknown[186.22.74.193]: 554 5.7.1 Service unavailable; Client host [186.22.74.193] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/186.22.74.193; from= to= proto=ESMTP helo=
2020-09-04 14:43:29
37.47.176.148 attack
Lines containing failures of 37.47.176.148
Sep  2 10:23:11 omfg postfix/smtpd[30643]: connect from public-gprs395603.centertel.pl[37.47.176.148]
Sep x@x
Sep  2 10:23:11 omfg postfix/smtpd[30643]: lost connection after DATA from public-gprs395603.centertel.pl[37.47.176.148]
Sep  2 10:23:11 omfg postfix/smtpd[30643]: disconnect from public-gprs395603.centertel.pl[37.47.176.148] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=37.47.176.148
2020-09-04 15:03:23
218.75.77.92 attackspam
$f2bV_matches
2020-09-04 15:00:57
105.235.135.204 attack
Sep  3 18:48:21 mellenthin postfix/smtpd[20928]: NOQUEUE: reject: RCPT from unknown[105.235.135.204]: 554 5.7.1 Service unavailable; Client host [105.235.135.204] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/105.235.135.204; from= to= proto=ESMTP helo=<[105.235.135.204]>
2020-09-04 14:36:07
192.241.222.97 attack
 TCP (SYN) 192.241.222.97:41951 -> port 7709, len 44
2020-09-04 14:31:50
222.186.175.163 attack
Sep  4 03:55:07 firewall sshd[2984]: Failed password for root from 222.186.175.163 port 53348 ssh2
Sep  4 03:55:10 firewall sshd[2984]: Failed password for root from 222.186.175.163 port 53348 ssh2
Sep  4 03:55:13 firewall sshd[2984]: Failed password for root from 222.186.175.163 port 53348 ssh2
...
2020-09-04 15:02:52
154.149.94.59 attack
Sep  3 18:48:14 debian64 sshd[10457]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.149.94.59 
Sep  3 18:48:16 debian64 sshd[10457]: Failed password for invalid user ubnt from 154.149.94.59 port 57600 ssh2
...
2020-09-04 14:38:52
209.45.91.26 attackspambots
Lines containing failures of 209.45.91.26 (max 1000)
Sep  2 10:22:39 mxbb sshd[12671]: Invalid user marcio from 209.45.91.26 port 34568
Sep  2 10:22:40 mxbb sshd[12671]: Failed password for invalid user marcio from 209.45.91.26 port 34568 ssh2
Sep  2 10:22:41 mxbb sshd[12671]: Received disconnect from 209.45.91.26 port 34568:11: Bye Bye [preauth]
Sep  2 10:22:41 mxbb sshd[12671]: Disconnected from 209.45.91.26 port 34568 [preauth]
Sep  2 10:29:01 mxbb sshd[12751]: Failed password for r.r from 209.45.91.26 port 48534 ssh2
Sep  2 10:29:01 mxbb sshd[12751]: Received disconnect from 209.45.91.26 port 48534:11: Bye Bye [preauth]
Sep  2 10:29:01 mxbb sshd[12751]: Disconnected from 209.45.91.26 port 48534 [preauth]
Sep  2 10:31:25 mxbb sshd[12819]: Failed password for ftp from 209.45.91.26 port 19562 ssh2
Sep  2 10:31:25 mxbb sshd[12819]: Received disconnect from 209.45.91.26 port 19562:11: Bye Bye [preauth]
Sep  2 10:31:25 mxbb sshd[12819]: Disconnected from 209.45.91.26 port ........
------------------------------
2020-09-04 15:13:33
112.85.42.73 attack
Sep  4 08:55:51 vps647732 sshd[20604]: Failed password for root from 112.85.42.73 port 43962 ssh2
...
2020-09-04 15:08:36
114.246.9.18 attack
Port Scan
...
2020-09-04 14:41:17

最近上报的IP列表

122.192.203.67 80.87.206.229 216.180.246.10 118.193.78.251
221.150.17.44 168.158.162.1 169.214.170.6 91.230.168.121
154.64.240.225 163.227.2.0 5.255.98.183 14.29.237.56
92.204.172.19 2606:4700:10::ac43:2613 192.168.31.197 2606:4700:10::6814:6677
38.134.104.24 47.94.164.88 118.193.37.50 2606:4700:10::6814:8773