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

城市(city): unknown

省份(region): unknown

国家(country): United States of America (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;54.81.113.196.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 05:30:20 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
196.113.81.54.in-addr.arpa domain name pointer ec2-54-81-113-196.compute-1.amazonaws.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
196.113.81.54.in-addr.arpa	name = ec2-54-81-113-196.compute-1.amazonaws.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
178.62.193.4 attackspam
xmlrpc attack
2019-11-24 21:42:16
92.118.38.55 attack
Nov 24 12:04:01 heicom postfix/smtpd\[31550\]: warning: unknown\[92.118.38.55\]: SASL LOGIN authentication failed: authentication failure
Nov 24 12:04:29 heicom postfix/smtpd\[30818\]: warning: unknown\[92.118.38.55\]: SASL LOGIN authentication failed: authentication failure
Nov 24 12:04:57 heicom postfix/smtpd\[31550\]: warning: unknown\[92.118.38.55\]: SASL LOGIN authentication failed: authentication failure
Nov 24 12:05:24 heicom postfix/smtpd\[30818\]: warning: unknown\[92.118.38.55\]: SASL LOGIN authentication failed: authentication failure
Nov 24 12:05:52 heicom postfix/smtpd\[31550\]: warning: unknown\[92.118.38.55\]: SASL LOGIN authentication failed: authentication failure
...
2019-11-24 21:22:16
45.82.153.135 attackspambots
Nov 24 14:31:33 relay postfix/smtpd\[22894\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:31:56 relay postfix/smtpd\[18484\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:33:25 relay postfix/smtpd\[23519\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:33:42 relay postfix/smtpd\[22894\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:47:01 relay postfix/smtpd\[23519\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-24 21:52:36
107.175.80.223 attackspambots
(From eric@talkwithcustomer.com) Hey,

You have a website whatcomchiropractic.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a
2019-11-24 21:29:42
111.231.109.151 attackbotsspam
Nov 24 08:34:29 ldap01vmsma01 sshd[28884]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.109.151
Nov 24 08:34:31 ldap01vmsma01 sshd[28884]: Failed password for invalid user witsoee from 111.231.109.151 port 33126 ssh2
...
2019-11-24 21:33:26
46.29.255.104 attackbotsspam
2019-11-24T07:18:02.356300 X postfix/smtpd[19811]: NOQUEUE: reject: RCPT from unknown[46.29.255.104]: 554 5.7.1 Service unavailable; Client host [46.29.255.104] blocked using zen.spamhaus.org; https://www.spamhaus.org/sbl/query/SBL224068; from= to= proto=ESMTP helo=
2019-11-24 21:48:23
123.232.156.28 attack
Nov 24 02:07:58 server sshd\[12629\]: Failed password for invalid user ftpuser from 123.232.156.28 port 42720 ssh2
Nov 24 09:05:47 server sshd\[24885\]: Invalid user backuppc from 123.232.156.28
Nov 24 09:05:47 server sshd\[24885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.232.156.28 
Nov 24 09:05:49 server sshd\[24885\]: Failed password for invalid user backuppc from 123.232.156.28 port 39443 ssh2
Nov 24 16:09:33 server sshd\[1924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.232.156.28  user=daemon
...
2019-11-24 21:45:57
37.14.240.100 attackspam
Nov 24 14:16:42 tux-35-217 sshd\[24327\]: Invalid user Matilda from 37.14.240.100 port 59590
Nov 24 14:16:42 tux-35-217 sshd\[24327\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.14.240.100
Nov 24 14:16:45 tux-35-217 sshd\[24327\]: Failed password for invalid user Matilda from 37.14.240.100 port 59590 ssh2
Nov 24 14:20:37 tux-35-217 sshd\[24332\]: Invalid user seo2010 from 37.14.240.100 port 39890
Nov 24 14:20:37 tux-35-217 sshd\[24332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.14.240.100
...
2019-11-24 21:23:26
187.177.165.225 attackspam
Automatic report - Port Scan Attack
2019-11-24 21:45:35
193.112.40.170 attackbotsspam
Nov 24 06:53:15 ms-srv sshd[49485]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.40.170
Nov 24 06:53:17 ms-srv sshd[49485]: Failed password for invalid user crepeau from 193.112.40.170 port 43914 ssh2
2019-11-24 21:21:22
185.234.219.113 attackbotsspam
Nov 24 13:27:01  postfix/smtpd: warning: unknown[185.234.219.113]: SASL LOGIN authentication failed
2019-11-24 21:38:33
172.73.190.156 attackspambots
Exploit Attempt
2019-11-24 21:55:21
51.68.228.85 attackbots
51.68.228.85 - - \[24/Nov/2019:12:11:09 +0100\] "POST /wp-login.php HTTP/1.0" 200 5707 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
51.68.228.85 - - \[24/Nov/2019:12:11:10 +0100\] "POST /wp-login.php HTTP/1.0" 200 5707 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
51.68.228.85 - - \[24/Nov/2019:12:11:10 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 802 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-24 21:54:15
90.84.224.75 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/90.84.224.75/ 
 
 RO - 1H : (12)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : RO 
 NAME ASN : ASN8953 
 
 IP : 90.84.224.75 
 
 CIDR : 90.84.224.0/20 
 
 PREFIX COUNT : 35 
 
 UNIQUE IP COUNT : 198656 
 
 
 ATTACKS DETECTED ASN8953 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-24 07:17:38 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-24 22:02:40
176.27.144.211 attackspam
Automatic report - Port Scan Attack
2019-11-24 21:38:13

最近上报的IP列表

210.240.248.63 75.121.48.85 142.225.6.78 128.175.222.4
225.35.118.182 199.16.241.122 92.106.175.114 100.50.238.180
88.159.139.48 192.40.176.6 177.230.184.43 138.254.236.163
120.217.88.53 27.247.1.69 179.40.119.152 140.73.154.100
123.132.145.123 208.207.192.158 170.217.83.203 193.41.79.226