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

城市(city): unknown

省份(region): unknown

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 20.50.146.106
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1275
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.50.146.106.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 23:22:06 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 106.146.50.20.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 106.146.50.20.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
104.254.92.218 attackbots
(From arek.josephine@outlook.com) Do away with credit card fees from your business forever details here: http://bit.ly/neverfees
2019-11-21 19:46:17
77.93.33.212 attack
Repeated brute force against a port
2019-11-21 20:18:43
49.80.63.136 attackspam
49.80.63.136 - - [21/Nov/2019:07:11:20 +0100] "GET / HTTP/1.1" 301 299 "-" "Googlebot/2.1 (+hxxp://www.googlebot.com/bot.html)"


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.80.63.136
2019-11-21 19:58:28
103.248.174.11 attackspambots
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-21 19:50:41
193.111.76.12 attackspambots
Nov 21 16:20:47 our-server-hostname postfix/smtpd[5015]: connect from unknown[193.111.76.12]
Nov x@x
Nov x@x
Nov 21 16:20:49 our-server-hostname postfix/smtpd[5015]: m3CB2A400DD: client=unknown[193.111.76.12]
Nov 21 16:20:50 our-server-hostname postfix/smtpd[13008]: 96324A400F7: client=unknown[127.0.0.1], orig_client=unknown[193.111.76.12]
Nov 21 16:20:50 our-server-hostname amavis[13707]: (13707-02) Passed CLEAN, [193.111.76.12] [193.111.76.12] , mail_id: E4W2Y1o0OXbw, Hhostnames: -, size: 14191, queued_as: 96324A400F7, 121 ms
Nov x@x
Nov x@x
Nov 21 16:20:50 our-server-hostname postfix/smtpd[5015]: D6263A400DD: client=unknown[193.111.76.12]
Nov 21 16:20:50 our-server-hostname postfix/smtpd[4826]: connect from unknown[193.111.76.12]
Nov 21 16:20:51 our-server-hostname postfix/smtpd[8788]: 5522DA400F7: client=unknown[127.0.0.1], orig_client=unknown[193.111.76.12]
Nov 21 16:20:51 our-server-hostname amavis[13349]: (13349-04) Passed CLEAN, [193.111.76.12] [193.111.76.........
-------------------------------
2019-11-21 19:44:16
111.231.237.245 attackbots
2019-11-21T06:56:30.626851abusebot-4.cloudsearch.cf sshd\[31423\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.237.245  user=root
2019-11-21 19:50:08
132.145.213.82 attack
Nov 21 12:44:28 dedicated sshd[23853]: Failed password for root from 132.145.213.82 port 32440 ssh2
Nov 21 12:47:56 dedicated sshd[24412]: Invalid user com** from 132.145.213.82 port 50409
Nov 21 12:47:56 dedicated sshd[24412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.145.213.82 
Nov 21 12:47:56 dedicated sshd[24412]: Invalid user com** from 132.145.213.82 port 50409
Nov 21 12:47:58 dedicated sshd[24412]: Failed password for invalid user com** from 132.145.213.82 port 50409 ssh2
2019-11-21 19:56:45
49.174.76.104 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-21 19:55:34
200.29.154.210 attackbotsspam
Unauthorised access (Nov 21) SRC=200.29.154.210 LEN=40 TTL=239 ID=45793 TCP DPT=445 WINDOW=1024 SYN 
Unauthorised access (Nov 19) SRC=200.29.154.210 LEN=40 TTL=239 ID=26260 TCP DPT=1433 WINDOW=1024 SYN
2019-11-21 20:20:27
78.5.35.54 attackspambots
Nov 21 07:06:23 xzibhostname postfix/smtpd[16563]: warning: hostname 78-5-35-54-static.albacom.net does not resolve to address 78.5.35.54: Name or service not known
Nov 21 07:06:23 xzibhostname postfix/smtpd[16563]: connect from unknown[78.5.35.54]
Nov 21 07:07:05 xzibhostname postfix/smtpd[16563]: SSL_accept error from unknown[78.5.35.54]: -1
Nov 21 07:07:05 xzibhostname postfix/smtpd[16563]: lost connection after STARTTLS from unknown[78.5.35.54]
Nov 21 07:07:05 xzibhostname postfix/smtpd[16563]: disconnect from unknown[78.5.35.54]
Nov 21 07:07:05 xzibhostname postfix/smtpd[16563]: warning: hostname 78-5-35-54-static.albacom.net does not resolve to address 78.5.35.54: Name or service not known
Nov 21 07:07:05 xzibhostname postfix/smtpd[16563]: connect from unknown[78.5.35.54]
Nov 21 07:07:08 xzibhostname postfix/smtpd[16563]: warning: unknown[78.5.35.54]: SASL PLAIN authentication failed: authentication failure
Nov 21 07:07:08 xzibhostname postfix/smtpd[16563]: warnin........
-------------------------------
2019-11-21 19:42:17
182.176.121.85 attackspam
Automatic report - Banned IP Access
2019-11-21 19:43:07
113.88.164.140 attackbotsspam
Nov 21 07:05:04 mxgate1 postfix/postscreen[7293]: CONNECT from [113.88.164.140]:51132 to [176.31.12.44]:25
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7297]: addr 113.88.164.140 listed by domain zen.spamhaus.org as 127.0.0.11
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7297]: addr 113.88.164.140 listed by domain zen.spamhaus.org as 127.0.0.3
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7297]: addr 113.88.164.140 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7296]: addr 113.88.164.140 listed by domain bl.spamcop.net as 127.0.0.2
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7298]: addr 113.88.164.140 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 21 07:05:04 mxgate1 postfix/dnsblog[7295]: addr 113.88.164.140 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 21 07:05:05 mxgate1 postfix/dnsblog[7294]: addr 113.88.164.140 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Nov 21 07:05:10 mxgate1 postfix/postscreen[7293]: DNSBL rank 6 for [113.........
-------------------------------
2019-11-21 19:36:59
220.135.232.45 attack
220.135.232.45 was recorded 5 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 5, 20, 24
2019-11-21 20:01:29
120.133.133.243 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-11-21 20:13:02
62.234.101.62 attack
SSH Bruteforce attack
2019-11-21 20:08:22

最近上报的IP列表

20.50.163.30 20.50.193.116 20.50.179.111 20.50.2.13
20.50.193.23 20.50.2.16 20.50.2.10 20.50.2.22
20.50.2.14 20.50.2.21 20.50.2.24 20.50.2.18
20.50.2.2 20.50.2.11 20.50.2.51 20.50.2.27
20.50.2.35 20.50.2.36 20.50.2.29 20.50.2.26