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

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

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


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

;; QUESTION SECTION:
;20.163.2.53.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 22 17:30:51 CST 2026
;; MSG SIZE  rcvd: 104
HOST信息:
Host 53.2.163.20.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 53.2.163.20.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
77.42.119.129 attackbots
Automatic report - Port Scan Attack
2019-07-19 06:46:11
34.196.177.230 attackbotsspam
Brute forcing RDP port 3389
2019-07-19 07:06:37
172.93.52.58 attackbots
Apr 14 23:29:30 vpn sshd[13945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.93.52.58  user=root
Apr 14 23:29:32 vpn sshd[13945]: Failed password for root from 172.93.52.58 port 36134 ssh2
Apr 14 23:29:33 vpn sshd[13948]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.93.52.58  user=root
Apr 14 23:29:34 vpn sshd[13948]: Failed password for root from 172.93.52.58 port 36286 ssh2
Apr 14 23:29:34 vpn sshd[13951]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.93.52.58  user=root
2019-07-19 07:03:37
173.249.33.121 attackbots
Mar 13 05:54:47 vpn sshd[13372]: Failed password for root from 173.249.33.121 port 42974 ssh2
Mar 13 06:00:24 vpn sshd[13413]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.249.33.121
Mar 13 06:00:26 vpn sshd[13413]: Failed password for invalid user support from 173.249.33.121 port 52146 ssh2
2019-07-19 06:47:11
171.98.3.186 attackspambots
Jun 26 10:36:26 vpn sshd[13014]: Invalid user vastvoices from 171.98.3.186
Jun 26 10:36:26 vpn sshd[13014]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.98.3.186
Jun 26 10:36:28 vpn sshd[13014]: Failed password for invalid user vastvoices from 171.98.3.186 port 42261 ssh2
Jun 26 10:36:30 vpn sshd[13014]: Failed password for invalid user vastvoices from 171.98.3.186 port 42261 ssh2
Jun 26 10:36:33 vpn sshd[13014]: Failed password for invalid user vastvoices from 171.98.3.186 port 42261 ssh2
2019-07-19 07:17:44
173.212.222.48 attackbots
Jul  6 19:57:47 vpn sshd[3919]: Invalid user apps from 173.212.222.48
Jul  6 19:57:47 vpn sshd[3919]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.212.222.48
Jul  6 19:57:48 vpn sshd[3919]: Failed password for invalid user apps from 173.212.222.48 port 46759 ssh2
Jul  6 19:59:43 vpn sshd[3922]: Invalid user deploy from 173.212.222.48
Jul  6 19:59:43 vpn sshd[3922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.212.222.48
2019-07-19 06:55:53
172.88.48.94 attackspambots
Mar 29 12:41:13 vpn sshd[6303]: Invalid user pi from 172.88.48.94
Mar 29 12:41:13 vpn sshd[6305]: Invalid user pi from 172.88.48.94
Mar 29 12:41:13 vpn sshd[6303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.88.48.94
Mar 29 12:41:13 vpn sshd[6305]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.88.48.94
Mar 29 12:41:15 vpn sshd[6303]: Failed password for invalid user pi from 172.88.48.94 port 44874 ssh2
2019-07-19 07:07:56
172.86.186.116 attackspam
Jun 19 23:03:40 vpn sshd[18055]: Invalid user guest from 172.86.186.116
Jun 19 23:03:40 vpn sshd[18055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.86.186.116
Jun 19 23:03:43 vpn sshd[18055]: Failed password for invalid user guest from 172.86.186.116 port 37264 ssh2
Jun 19 23:05:23 vpn sshd[18057]: Invalid user matt from 172.86.186.116
Jun 19 23:05:23 vpn sshd[18057]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.86.186.116
2019-07-19 07:08:16
151.30.1.100 attackspam
Jul 18 23:07:22 vps65 sshd\[8715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.30.1.100  user=root
Jul 18 23:07:24 vps65 sshd\[8715\]: Failed password for root from 151.30.1.100 port 59390 ssh2
...
2019-07-19 07:23:48
211.240.105.132 attackspambots
2019-07-19T00:48:35.556407lon01.zurich-datacenter.net sshd\[9301\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.240.105.132  user=root
2019-07-19T00:48:37.887633lon01.zurich-datacenter.net sshd\[9301\]: Failed password for root from 211.240.105.132 port 51454 ssh2
2019-07-19T00:53:04.714564lon01.zurich-datacenter.net sshd\[9367\]: Invalid user admin from 211.240.105.132 port 43804
2019-07-19T00:53:04.720728lon01.zurich-datacenter.net sshd\[9367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.240.105.132
2019-07-19T00:53:05.978301lon01.zurich-datacenter.net sshd\[9367\]: Failed password for invalid user admin from 211.240.105.132 port 43804 ssh2
...
2019-07-19 07:00:03
201.77.115.128 attackspambots
Jul 19 04:19:09 vibhu-HP-Z238-Microtower-Workstation sshd\[21972\]: Invalid user angel from 201.77.115.128
Jul 19 04:19:09 vibhu-HP-Z238-Microtower-Workstation sshd\[21972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.77.115.128
Jul 19 04:19:10 vibhu-HP-Z238-Microtower-Workstation sshd\[21972\]: Failed password for invalid user angel from 201.77.115.128 port 47442 ssh2
Jul 19 04:24:55 vibhu-HP-Z238-Microtower-Workstation sshd\[22181\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.77.115.128  user=root
Jul 19 04:24:57 vibhu-HP-Z238-Microtower-Workstation sshd\[22181\]: Failed password for root from 201.77.115.128 port 44918 ssh2
...
2019-07-19 07:04:43
173.208.136.122 attackspam
Dec 16 05:53:25 vpn sshd[6541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.208.136.122
Dec 16 05:53:28 vpn sshd[6541]: Failed password for invalid user amavis from 173.208.136.122 port 40872 ssh2
Dec 16 06:01:47 vpn sshd[6601]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.208.136.122
2019-07-19 06:59:13
129.121.16.69 attack
scam
2019-07-19 07:02:51
45.116.232.52 attackbotsspam
45.116.232.52 - - \[18/Jul/2019:21:03:23 +0000\] "POST /xmlrpc.php HTTP/1.1" 301 603 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"
45.116.232.52 - - \[18/Jul/2019:21:04:24 +0000\] "POST /xmlrpc.php HTTP/1.1" 301 603 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"
45.116.232.52 - - \[18/Jul/2019:21:05:25 +0000\] "POST /xmlrpc.php HTTP/1.1" 301 603 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"
45.116.232.52 - - \[18/Jul/2019:21:06:27 +0000\] "POST /xmlrpc.php HTTP/1.1" 301 603 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"
45.116.232.52 - - \[18/Jul/2019:21:07:28 +0000\] "POST /xmlrpc.php HTTP/1.1" 301 603 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"
2019-07-19 07:21:36
46.101.43.224 attack
Jul 19 00:08:37 localhost sshd\[2220\]: Invalid user user from 46.101.43.224 port 36468
Jul 19 00:08:37 localhost sshd\[2220\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.43.224
...
2019-07-19 07:10:17

最近上报的IP列表

183.29.124.76 183.155.112.167 183.147.87.196 171.212.223.2
144.255.40.112 123.169.108.99 122.230.32.170 117.69.37.9
115.211.114.151 114.106.99.168 124.111.27.246 66.163.119.231
168.56.42.229 62.210.136.56 209.38.224.31 90.56.225.96
216.180.246.68 34.198.1.205 45.119.85.39 135.237.125.182