必须是合法有效的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 <<>> 140.4.193.19
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20639
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;140.4.193.19.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 11:20:33 CST 2025
;; MSG SIZE  rcvd: 105
HOST信息:
Host 19.193.4.140.in-addr.arpa not found: 2(SERVFAIL)
NSLOOKUP信息:
server can't find 140.4.193.19.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
198.108.67.34 attackbotsspam
firewall-block, port(s): 1063/tcp
2019-07-07 15:33:30
73.2.139.100 attackspambots
Reported by AbuseIPDB proxy server.
2019-07-07 15:30:21
122.100.92.20 attackbotsspam
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-07 06:42:41,622 INFO [amun_request_handler] PortScan Detected on Port: 445 (122.100.92.20)
2019-07-07 16:11:35
80.82.67.111 attackbotsspam
Jul  7 07:13:36 mail postfix/smtpd\[1363\]: warning: unknown\[80.82.67.111\]: SASL PLAIN authentication failed: \
Jul  7 07:39:49 mail postfix/smtpd\[1795\]: warning: unknown\[80.82.67.111\]: SASL PLAIN authentication failed: \
Jul  7 07:49:31 mail postfix/smtpd\[1958\]: warning: unknown\[80.82.67.111\]: SASL PLAIN authentication failed: \
Jul  7 08:58:19 mail postfix/smtpd\[3194\]: warning: unknown\[80.82.67.111\]: SASL PLAIN authentication failed: \
2019-07-07 15:40:08
51.255.26.166 attackspambots
Jul  7 07:56:30 ArkNodeAT sshd\[18854\]: Invalid user zarko from 51.255.26.166
Jul  7 07:56:30 ArkNodeAT sshd\[18854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.26.166
Jul  7 07:56:32 ArkNodeAT sshd\[18854\]: Failed password for invalid user zarko from 51.255.26.166 port 34368 ssh2
2019-07-07 15:56:06
111.230.247.243 attack
Jul  7 07:03:26 Ubuntu-1404-trusty-64-minimal sshd\[8281\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.247.243  user=www-data
Jul  7 07:03:27 Ubuntu-1404-trusty-64-minimal sshd\[8281\]: Failed password for www-data from 111.230.247.243 port 42339 ssh2
Jul  7 07:07:39 Ubuntu-1404-trusty-64-minimal sshd\[10074\]: Invalid user testing from 111.230.247.243
Jul  7 07:07:39 Ubuntu-1404-trusty-64-minimal sshd\[10074\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.247.243
Jul  7 07:07:41 Ubuntu-1404-trusty-64-minimal sshd\[10074\]: Failed password for invalid user testing from 111.230.247.243 port 32982 ssh2
2019-07-07 15:21:03
23.94.148.157 attack
(From eric@talkwithcustomer.com) Hello zchiro.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website zchiro.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website zchiro.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer put it, “you’re
2019-07-07 15:59:59
62.78.81.28 attack
Port scan on 3 port(s): 1024 8000 8080
2019-07-07 15:35:48
113.73.144.139 attackbots
Banned for posting to wp-login.php without referer {"redirect_to":"http:\/\/youinmiami.com\/wp-admin\/theme-install.php","wp-submit":"Log In","pwd":"admin1","testcookie":"1","log":"admin"}
2019-07-07 15:47:37
54.38.154.25 attackbots
5060/udp 5060/udp 5060/udp...
[2019-06-22/07-06]88pkt,1pt.(udp)
2019-07-07 16:06:30
140.143.239.156 attackspambots
Jul  7 08:43:01 icinga sshd[13427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.239.156
Jul  7 08:43:03 icinga sshd[13427]: Failed password for invalid user test1 from 140.143.239.156 port 50820 ssh2
...
2019-07-07 15:39:24
185.216.132.15 attackbotsspam
Jul  7 07:42:22 heissa sshd\[13652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.216.132.15  user=root
Jul  7 07:42:24 heissa sshd\[13652\]: Failed password for root from 185.216.132.15 port 7546 ssh2
Jul  7 07:42:24 heissa sshd\[13654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.216.132.15  user=root
Jul  7 07:42:26 heissa sshd\[13654\]: Failed password for root from 185.216.132.15 port 8028 ssh2
Jul  7 07:42:26 heissa sshd\[13656\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.216.132.15  user=root
2019-07-07 15:22:06
221.124.215.74 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2019-07-07 15:29:25
123.207.237.192 attack
firewall-block, port(s): 445/tcp
2019-07-07 15:38:03
128.199.165.124 attack
8545/tcp 8545/tcp 8545/tcp...
[2019-05-07/07-06]300pkt,1pt.(tcp)
2019-07-07 16:12:49

最近上报的IP列表

115.92.101.106 202.71.208.1 198.32.25.59 27.29.247.164
186.2.234.76 40.10.131.106 7.90.97.193 156.79.209.34
124.18.15.65 115.106.149.78 16.217.84.14 74.45.1.105
118.193.229.255 39.5.192.144 126.238.103.0 26.250.211.53
242.71.67.159 227.54.61.9 28.17.39.40 7.95.250.140