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

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


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

;; QUESTION SECTION:
;20.168.123.59.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Nov 11 12:01:27 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
59.123.168.20.in-addr.arpa domain name pointer azpdwsnfnxee.stretchoid.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
59.123.168.20.in-addr.arpa	name = azpdwsnfnxee.stretchoid.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
69.51.205.179 attack
Dec 20 15:07:51 vpn sshd[15044]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.51.205.179
Dec 20 15:07:53 vpn sshd[15044]: Failed password for invalid user demouser from 69.51.205.179 port 56308 ssh2
Dec 20 15:16:10 vpn sshd[15080]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.51.205.179
2020-01-05 16:25:24
77.42.75.210 attack
Automatic report - Port Scan Attack
2020-01-05 16:04:39
72.175.38.52 attackbots
Mar 22 11:36:32 vpn sshd[26608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.175.38.52
Mar 22 11:36:34 vpn sshd[26608]: Failed password for invalid user discover from 72.175.38.52 port 47002 ssh2
Mar 22 11:46:01 vpn sshd[26668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.175.38.52
2020-01-05 15:52:37
70.105.173.75 attackspambots
Mar 20 00:49:25 vpn sshd[6303]: Invalid user smbuser from 70.105.173.75
Mar 20 00:49:25 vpn sshd[6303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.105.173.75
Mar 20 00:49:27 vpn sshd[6303]: Failed password for invalid user smbuser from 70.105.173.75 port 53556 ssh2
Mar 20 00:50:42 vpn sshd[6306]: Invalid user programmer from 70.105.173.75
Mar 20 00:50:42 vpn sshd[6306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.105.173.75
2020-01-05 16:18:49
70.54.205.127 attack
Feb 23 14:38:25 vpn sshd[26404]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.54.205.127
Feb 23 14:38:27 vpn sshd[26404]: Failed password for invalid user teampspeak from 70.54.205.127 port 35269 ssh2
Feb 23 14:42:15 vpn sshd[26446]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.54.205.127
2020-01-05 16:09:27
196.218.42.200 attackbots
(mod_security) mod_security (id:230011) triggered by 196.218.42.200 (EG/Egypt/host-196.218.42.200-static.tedata.net): 5 in the last 3600 secs
2020-01-05 16:32:42
71.39.23.248 attack
Nov 21 07:38:25 vpn sshd[8157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.39.23.248
Nov 21 07:38:27 vpn sshd[8157]: Failed password for invalid user elastic from 71.39.23.248 port 51002 ssh2
Nov 21 07:47:06 vpn sshd[8195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.39.23.248
2020-01-05 15:58:58
70.45.72.88 attackbotsspam
Mar  6 19:20:53 vpn sshd[27608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.45.72.88
Mar  6 19:20:55 vpn sshd[27608]: Failed password for invalid user gj from 70.45.72.88 port 33048 ssh2
Mar  6 19:27:57 vpn sshd[27696]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.45.72.88
2020-01-05 16:10:56
115.78.94.97 attackspam
Fail2Ban Ban Triggered
2020-01-05 16:19:19
70.79.78.233 attackspam
Mar 21 12:30:34 vpn sshd[3810]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.79.78.233
Mar 21 12:30:37 vpn sshd[3810]: Failed password for invalid user hans from 70.79.78.233 port 44616 ssh2
Mar 21 12:39:23 vpn sshd[3836]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=70.79.78.233
2020-01-05 16:08:00
71.175.65.206 attackbots
Mar 22 16:13:26 vpn sshd[27538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.175.65.206
Mar 22 16:13:28 vpn sshd[27538]: Failed password for invalid user weblogic from 71.175.65.206 port 55358 ssh2
Mar 22 16:18:58 vpn sshd[27574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.175.65.206
2020-01-05 16:02:26
112.85.42.188 attack
01/05/2020-03:17:02.899551 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-05 16:17:33
72.177.27.90 attack
Jan 25 19:22:25 vpn sshd[8912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.177.27.90
Jan 25 19:22:26 vpn sshd[8912]: Failed password for invalid user jader from 72.177.27.90 port 49710 ssh2
Jan 25 19:27:34 vpn sshd[8919]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.177.27.90
2020-01-05 15:52:05
69.36.61.251 attack
Dec 23 15:12:42 vpn sshd[18250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.36.61.251
Dec 23 15:12:43 vpn sshd[18250]: Failed password for invalid user ivo from 69.36.61.251 port 52617 ssh2
Dec 23 15:16:18 vpn sshd[18275]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.36.61.251
2020-01-05 16:29:40
69.51.13.243 attackspam
Mar 21 03:04:49 vpn sshd[1125]: Failed password for root from 69.51.13.243 port 41592 ssh2
Mar 21 03:09:13 vpn sshd[1133]: Failed password for root from 69.51.13.243 port 46676 ssh2
2020-01-05 16:28:34

最近上报的IP列表

20.80.76.6 38.80.191.40 159.89.85.160 211.161.118.27
27.219.57.217 221.215.8.7 15.204.87.212 143.244.53.219
124.207.169.3 35.210.176.64 86.38.187.56 35.210.39.84
200.138.46.70 200.138.46.69 200.138.46.25 66.132.159.102
34.151.154.26 20.127.191.36 175.107.228.197 172.241.38.116