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

城市(city): Pune

省份(region): Maharashtra

国家(country): India

运营商(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.192.0.0 - 20.255.255.255
CIDR:           20.192.0.0/10
NetName:        MSFT
NetHandle:      NET-20-192-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.192.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


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

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

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-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.219.32.156
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57621
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.219.32.156.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 22 05:00:02 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 156.32.219.20.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 156.32.219.20.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
113.125.159.5 attackbots
May 23 22:57:39 piServer sshd[718]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.159.5 
May 23 22:57:40 piServer sshd[718]: Failed password for invalid user deh from 113.125.159.5 port 37860 ssh2
May 23 23:00:50 piServer sshd[972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.159.5 
...
2020-05-24 05:05:01
112.35.57.139 attackbots
2020-05-23T20:11:11.830423abusebot-3.cloudsearch.cf sshd[5653]: Invalid user qli from 112.35.57.139 port 38234
2020-05-23T20:11:11.836291abusebot-3.cloudsearch.cf sshd[5653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.57.139
2020-05-23T20:11:11.830423abusebot-3.cloudsearch.cf sshd[5653]: Invalid user qli from 112.35.57.139 port 38234
2020-05-23T20:11:14.383518abusebot-3.cloudsearch.cf sshd[5653]: Failed password for invalid user qli from 112.35.57.139 port 38234 ssh2
2020-05-23T20:15:18.385462abusebot-3.cloudsearch.cf sshd[5896]: Invalid user mlz from 112.35.57.139 port 36658
2020-05-23T20:15:18.396110abusebot-3.cloudsearch.cf sshd[5896]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.57.139
2020-05-23T20:15:18.385462abusebot-3.cloudsearch.cf sshd[5896]: Invalid user mlz from 112.35.57.139 port 36658
2020-05-23T20:15:20.517051abusebot-3.cloudsearch.cf sshd[5896]: Failed password for inva
...
2020-05-24 05:05:18
54.37.226.123 attackspambots
May 23 23:04:59 h2779839 sshd[17584]: Invalid user ivt from 54.37.226.123 port 50600
May 23 23:04:59 h2779839 sshd[17584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.226.123
May 23 23:04:59 h2779839 sshd[17584]: Invalid user ivt from 54.37.226.123 port 50600
May 23 23:05:01 h2779839 sshd[17584]: Failed password for invalid user ivt from 54.37.226.123 port 50600 ssh2
May 23 23:09:04 h2779839 sshd[17676]: Invalid user jpm from 54.37.226.123 port 55540
May 23 23:09:04 h2779839 sshd[17676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.226.123
May 23 23:09:04 h2779839 sshd[17676]: Invalid user jpm from 54.37.226.123 port 55540
May 23 23:09:06 h2779839 sshd[17676]: Failed password for invalid user jpm from 54.37.226.123 port 55540 ssh2
May 23 23:12:46 h2779839 sshd[17740]: Invalid user xio from 54.37.226.123 port 60478
...
2020-05-24 05:26:50
120.24.56.245 attack
WordPress brute force
2020-05-24 05:15:32
114.190.42.34 attackbotsspam
Unauthorized connection attempt from IP address 114.190.42.34 on Port 445(SMB)
2020-05-24 05:20:41
45.142.195.14 attack
May 23 22:15:35 blackbee postfix/smtpd\[24080\]: warning: unknown\[45.142.195.14\]: SASL LOGIN authentication failed: authentication failure
May 23 22:16:00 blackbee postfix/smtpd\[24080\]: warning: unknown\[45.142.195.14\]: SASL LOGIN authentication failed: authentication failure
May 23 22:16:26 blackbee postfix/smtpd\[24080\]: warning: unknown\[45.142.195.14\]: SASL LOGIN authentication failed: authentication failure
May 23 22:16:53 blackbee postfix/smtpd\[24052\]: warning: unknown\[45.142.195.14\]: SASL LOGIN authentication failed: authentication failure
May 23 22:17:18 blackbee postfix/smtpd\[24080\]: warning: unknown\[45.142.195.14\]: SASL LOGIN authentication failed: authentication failure
...
2020-05-24 05:35:50
45.40.166.148 attack
C1,WP GET /lappan/new/wp-includes/wlwmanifest.xml
2020-05-24 05:30:02
123.254.228.123 attack
Port probing on unauthorized port 23
2020-05-24 05:34:45
88.218.17.157 attackspam
Unauthorized connection attempt from IP address 88.218.17.157 on Port 3389(RDP)
2020-05-24 05:23:23
94.102.50.137 attackbotsspam
May 23 22:14:44 debian-2gb-nbg1-2 kernel: \[12523695.612299\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.50.137 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=23583 PROTO=TCP SPT=42253 DPT=20027 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-24 05:43:11
67.207.88.180 attackspam
May 23 22:15:16 ncomp sshd[27734]: Invalid user xbr from 67.207.88.180
May 23 22:15:16 ncomp sshd[27734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.207.88.180
May 23 22:15:16 ncomp sshd[27734]: Invalid user xbr from 67.207.88.180
May 23 22:15:17 ncomp sshd[27734]: Failed password for invalid user xbr from 67.207.88.180 port 49922 ssh2
2020-05-24 05:10:42
202.88.234.140 attackbots
Invalid user tra from 202.88.234.140 port 52640
2020-05-24 05:36:13
201.27.117.106 attackspam
Unauthorized connection attempt from IP address 201.27.117.106 on Port 445(SMB)
2020-05-24 05:06:22
52.67.191.166 attackspam
WordPress brute force
2020-05-24 05:20:00
112.85.42.89 attack
May 23 23:19:27 piServer sshd[2527]: Failed password for root from 112.85.42.89 port 49216 ssh2
May 23 23:19:31 piServer sshd[2527]: Failed password for root from 112.85.42.89 port 49216 ssh2
May 23 23:19:34 piServer sshd[2527]: Failed password for root from 112.85.42.89 port 49216 ssh2
...
2020-05-24 05:29:23

最近上报的IP列表

39.98.56.161 47.92.23.206 69.85.11.202 20.78.132.16
8.211.154.34 199.168.138.224 199.168.138.19 199.168.138.182
199.168.138.186 194.187.177.251 80.248.237.100 193.183.76.118
35.203.211.87 121.43.125.129 98.81.182.10 47.99.50.46
87.236.176.169 192.36.109.82 192.36.109.102 172.232.108.36