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

城市(city): unknown

省份(region): unknown

国家(country): Korea (the Republic of)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;49.18.56.131.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 23:21:12 CST 2025
;; MSG SIZE  rcvd: 105
HOST信息:
Host 131.56.18.49.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 131.56.18.49.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
118.24.123.34 attackbotsspam
Aug 28 15:01:18 pkdns2 sshd\[31468\]: Invalid user yy from 118.24.123.34Aug 28 15:01:20 pkdns2 sshd\[31468\]: Failed password for invalid user yy from 118.24.123.34 port 39718 ssh2Aug 28 15:04:12 pkdns2 sshd\[31585\]: Invalid user splunk from 118.24.123.34Aug 28 15:04:15 pkdns2 sshd\[31585\]: Failed password for invalid user splunk from 118.24.123.34 port 44236 ssh2Aug 28 15:07:10 pkdns2 sshd\[31784\]: Failed password for zabbix from 118.24.123.34 port 48758 ssh2Aug 28 15:10:03 pkdns2 sshd\[31915\]: Failed password for root from 118.24.123.34 port 53280 ssh2
...
2020-08-28 20:10:49
49.233.180.151 attackspam
Fail2Ban
2020-08-28 20:33:44
64.227.37.93 attackspam
B: f2b ssh aggressive 3x
2020-08-28 20:35:44
211.253.24.250 attack
Invalid user nara from 211.253.24.250 port 38600
2020-08-28 20:05:15
193.35.51.20 attack
Aug 28 14:40:26 galaxy event: galaxy/lswi: smtp: tom@wirtschaftsinformatik-potsdam.de [193.35.51.20] authentication failure using internet password
Aug 28 14:40:29 galaxy event: galaxy/lswi: smtp: tom [193.35.51.20] authentication failure using internet password
Aug 28 14:40:34 galaxy event: galaxy/lswi: smtp: philip@wirtschaftsinformatik-potsdam.de [193.35.51.20] authentication failure using internet password
Aug 28 14:40:34 galaxy event: galaxy/lswi: smtp: joachim@wirtschaftsinformatik-potsdam.de [193.35.51.20] authentication failure using internet password
Aug 28 14:40:35 galaxy event: galaxy/lswi: smtp: philip [193.35.51.20] authentication failure using internet password
...
2020-08-28 20:40:52
134.122.111.162 attackspam
Aug 28 14:09:49 vm0 sshd[9920]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.111.162
Aug 28 14:09:52 vm0 sshd[9920]: Failed password for invalid user zbh from 134.122.111.162 port 60656 ssh2
...
2020-08-28 20:26:38
104.45.88.60 attack
2020-08-28T07:09:52.499031morrigan.ad5gb.com sshd[2853105]: Failed password for invalid user newuser from 104.45.88.60 port 43522 ssh2
2020-08-28T07:09:52.974595morrigan.ad5gb.com sshd[2853105]: Disconnected from invalid user newuser 104.45.88.60 port 43522 [preauth]
2020-08-28 20:23:53
75.75.235.21 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found docstone.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software that can l
2020-08-28 20:08:19
165.22.113.66 attackbots
2020-08-28T07:09:53.534215morrigan.ad5gb.com sshd[2853110]: Invalid user simon from 165.22.113.66 port 54400
2020-08-28T07:09:55.847021morrigan.ad5gb.com sshd[2853110]: Failed password for invalid user simon from 165.22.113.66 port 54400 ssh2
2020-08-28 20:22:40
111.229.190.8 attack
2020-08-28T07:09:56.552043morrigan.ad5gb.com sshd[2853108]: Failed password for daemon from 111.229.190.8 port 38128 ssh2
2020-08-28T07:09:58.207633morrigan.ad5gb.com sshd[2853108]: Disconnected from authenticating user daemon 111.229.190.8 port 38128 [preauth]
2020-08-28 20:18:33
106.13.79.109 attackbotsspam
Aug 26 02:27:54 our-server-hostname sshd[32185]: Invalid user zzh from 106.13.79.109
Aug 26 02:27:54 our-server-hostname sshd[32185]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.79.109 
Aug 26 02:27:56 our-server-hostname sshd[32185]: Failed password for invalid user zzh from 106.13.79.109 port 59102 ssh2
Aug 26 02:46:11 our-server-hostname sshd[2712]: Invalid user import from 106.13.79.109
Aug 26 02:46:11 our-server-hostname sshd[2712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.79.109 
Aug 26 02:46:13 our-server-hostname sshd[2712]: Failed password for invalid user import from 106.13.79.109 port 54796 ssh2
Aug 26 02:50:07 our-server-hostname sshd[3528]: Did not receive identification string from 106.13.79.109
Aug 26 02:57:38 our-server-hostname sshd[5033]: Invalid user claudia from 106.13.79.109
Aug 26 02:57:38 our-server-hostname sshd[5033]: pam_unix(sshd:auth): aut........
-------------------------------
2020-08-28 20:28:47
157.230.19.72 attackbots
SSH bruteforce
2020-08-28 20:38:30
103.125.191.136 attackspam
2020-08-28 07:06:09.898552-0500  localhost sshd[34727]: Failed password for guest from 103.125.191.136 port 57199 ssh2
2020-08-28 20:13:43
212.70.149.4 attackbotsspam
Aug 28 14:29:26 relay postfix/smtpd\[24160\]: warning: unknown\[212.70.149.4\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 28 14:32:45 relay postfix/smtpd\[24561\]: warning: unknown\[212.70.149.4\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 28 14:36:03 relay postfix/smtpd\[25739\]: warning: unknown\[212.70.149.4\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 28 14:39:22 relay postfix/smtpd\[27387\]: warning: unknown\[212.70.149.4\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 28 14:42:42 relay postfix/smtpd\[29449\]: warning: unknown\[212.70.149.4\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-08-28 20:44:02
198.199.84.104 attack
2020-08-28 07:08:25.293416-0500  localhost sshd[34944]: Failed password for invalid user leon from 198.199.84.104 port 59384 ssh2
2020-08-28 20:12:26

最近上报的IP列表

46.183.15.130 109.222.59.11 239.8.38.190 132.249.81.82
32.53.43.49 98.69.186.255 230.60.225.46 161.61.220.114
38.233.3.98 37.67.252.58 33.13.159.36 56.196.199.14
69.152.121.139 72.125.57.217 123.38.232.252 211.65.105.228
66.95.14.120 79.63.4.24 60.5.155.139 86.158.18.222