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

城市(city): Nagpur

省份(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

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

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

;; QUESTION SECTION:
;20.192.194.67.			IN	A

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

;; Query time: 3 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 23 16:43:14 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 67.194.192.20.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 67.194.192.20.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
148.70.212.162 attackspambots
Jan  3 06:48:35 web9 sshd\[24815\]: Invalid user splunk from 148.70.212.162
Jan  3 06:48:35 web9 sshd\[24815\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.212.162
Jan  3 06:48:36 web9 sshd\[24815\]: Failed password for invalid user splunk from 148.70.212.162 port 40340 ssh2
Jan  3 06:53:25 web9 sshd\[25540\]: Invalid user postgres from 148.70.212.162
Jan  3 06:53:25 web9 sshd\[25540\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.212.162
2020-01-04 01:21:19
151.80.47.9 attackspambots
Jan  3 14:02:33 debian-2gb-nbg1-2 kernel: \[315880.170675\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=151.80.47.9 DST=195.201.40.59 LEN=52 TOS=0x16 PREC=0x00 TTL=116 ID=2657 DF PROTO=TCP SPT=52574 DPT=52 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0
2020-01-04 01:27:45
106.12.78.161 attackspambots
Automatic report - Banned IP Access
2020-01-04 01:34:24
182.65.8.168 attackspam
Lines containing failures of 182.65.8.168
Jan  3 13:49:59 omfg postfix/smtpd[8115]: connect from unknown[182.65.8.168]
Jan x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=182.65.8.168
2020-01-04 01:39:24
128.1.137.34 attack
Repeated brute force against a port
2020-01-04 01:18:03
123.206.90.149 attackbots
Jan  3 11:31:58 ldap01vmsma01 sshd[128910]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.90.149
Jan  3 11:32:00 ldap01vmsma01 sshd[128910]: Failed password for invalid user aecpro from 123.206.90.149 port 55472 ssh2
...
2020-01-04 01:28:06
129.204.108.143 attack
ssh failed login
2020-01-04 01:50:42
119.123.219.236 attackspambots
Jan  3 13:58:14 srv01 sshd[22870]: Invalid user stef from 119.123.219.236 port 2168
Jan  3 13:58:14 srv01 sshd[22870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.219.236
Jan  3 13:58:14 srv01 sshd[22870]: Invalid user stef from 119.123.219.236 port 2168
Jan  3 13:58:16 srv01 sshd[22870]: Failed password for invalid user stef from 119.123.219.236 port 2168 ssh2
Jan  3 14:01:57 srv01 sshd[23149]: Invalid user wpyan from 119.123.219.236 port 2169
...
2020-01-04 01:49:40
124.171.142.195 attackbots
Jan  3 22:38:10 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 22:38:20 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 22:45:32 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 22:45:42 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 22:53:26 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 22:53:38 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=124.171.142.195 
Jan  3 23:15:49 apex-mail dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=........
-------------------------------
2020-01-04 01:10:13
195.128.100.65 attack
SSH/22 MH Probe, BF, Hack -
2020-01-04 01:34:55
188.131.174.3 attackspam
(sshd) Failed SSH login from 188.131.174.3 (CN/China/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Jan  3 08:02:54 host sshd[99511]: Invalid user cuigj from 188.131.174.3 port 55132
2020-01-04 01:10:50
222.186.175.182 attackbotsspam
Jan  3 18:30:28 silence02 sshd[30463]: Failed password for root from 222.186.175.182 port 56524 ssh2
Jan  3 18:30:44 silence02 sshd[30463]: error: maximum authentication attempts exceeded for root from 222.186.175.182 port 56524 ssh2 [preauth]
Jan  3 18:30:51 silence02 sshd[30608]: Failed password for root from 222.186.175.182 port 20654 ssh2
2020-01-04 01:42:06
51.75.27.78 attackbotsspam
Jan  3 16:47:42 legacy sshd[28463]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.27.78
Jan  3 16:47:44 legacy sshd[28463]: Failed password for invalid user design from 51.75.27.78 port 49858 ssh2
Jan  3 16:50:54 legacy sshd[28558]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.27.78
...
2020-01-04 01:18:45
223.71.167.164 attackbotsspam
Unauthorized connection attempt detected from IP address 223.71.167.164 to port 6668
2020-01-04 01:29:50
139.59.9.234 attack
Jan  3 14:00:24 roki sshd[32502]: Invalid user tuserver from 139.59.9.234
Jan  3 14:00:24 roki sshd[32502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.9.234
Jan  3 14:00:26 roki sshd[32502]: Failed password for invalid user tuserver from 139.59.9.234 port 46850 ssh2
Jan  3 14:12:51 roki sshd[897]: Invalid user ubnt from 139.59.9.234
Jan  3 14:12:51 roki sshd[897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.9.234
...
2020-01-04 01:06:00

最近上报的IP列表

210.72.145.44 206.189.3.226 5.104.84.79 123.173.3.216
10.7.28.241 223.101.45.207 20.14.87.238 48.217.82.99
167.172.91.71 172.237.117.22 172.237.117.159 220.195.106.175
111.57.88.52 127.120.36.12 199.45.155.81 115.45.40.107
167.88.164.159 159.223.168.77 185.247.137.49 143.198.122.12