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

城市(city): Redmond

省份(region): Washington

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;138.196.89.145.			IN	A

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

;; Query time: 115 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 03:40:18 CST 2020
;; MSG SIZE  rcvd: 118
HOST信息:
Host 145.89.196.138.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 145.89.196.138.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
77.247.110.166 attack
\[2019-12-21 17:58:26\] NOTICE\[2839\] chan_sip.c: Registration from '"8008" \' failed for '77.247.110.166:5390' - Wrong password
\[2019-12-21 17:58:26\] SECURITY\[2857\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-12-21T17:58:26.779-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="8008",SessionID="0x7f0fb49f48b8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.166/5390",Challenge="3cc795b4",ReceivedChallenge="3cc795b4",ReceivedHash="4d030a4227f1b493437af012184d288b"
\[2019-12-21 17:58:26\] NOTICE\[2839\] chan_sip.c: Registration from '"8008" \' failed for '77.247.110.166:5390' - Wrong password
\[2019-12-21 17:58:26\] SECURITY\[2857\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-12-21T17:58:26.879-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="8008",SessionID="0x7f0fb4a5a908",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4
2019-12-22 07:05:21
51.15.118.15 attackspam
Invalid user sunos from 51.15.118.15 port 53228
2019-12-22 07:15:22
222.186.173.142 attackspam
Dec 21 23:30:02 thevastnessof sshd[7555]: Failed password for root from 222.186.173.142 port 58318 ssh2
...
2019-12-22 07:34:39
46.38.144.146 attack
Dec 21 22:53:42 blackbee postfix/smtpd\[26037\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Dec 21 22:54:52 blackbee postfix/smtpd\[26037\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Dec 21 22:56:02 blackbee postfix/smtpd\[26037\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Dec 21 22:57:10 blackbee postfix/smtpd\[26071\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Dec 21 22:58:18 blackbee postfix/smtpd\[26071\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
...
2019-12-22 07:21:53
49.234.28.54 attack
Dec 21 22:58:05 work-partkepr sshd\[13103\]: User daemon from 49.234.28.54 not allowed because not listed in AllowUsers
Dec 21 22:58:05 work-partkepr sshd\[13103\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.28.54  user=daemon
...
2019-12-22 07:39:19
23.94.32.16 attackbotsspam
(From eric@talkwithcustomer.com) 
Hi,

Let’s take a quick trip to Tomorrow-land.

I’m not talking about a theme park, I’m talking about your business’s future…

Don’t worry, we won’t even need a crystal ball.  

Just imagine… 

… a future where the money you invest in driving traffic to your site bissland.com pays off with tons of calls from qualified leads.
 
And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website bissland.com.  Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets.

Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference?

And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer.

You installed TalkWithCustomer on bissland.com – it was a snap.

And practically overnight customers started engaging more r
2019-12-22 07:06:02
106.52.234.191 attackspam
Dec 21 13:13:29 php1 sshd\[15959\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.234.191  user=root
Dec 21 13:13:31 php1 sshd\[15959\]: Failed password for root from 106.52.234.191 port 51707 ssh2
Dec 21 13:18:34 php1 sshd\[16595\]: Invalid user kendle from 106.52.234.191
Dec 21 13:18:34 php1 sshd\[16595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.234.191
Dec 21 13:18:36 php1 sshd\[16595\]: Failed password for invalid user kendle from 106.52.234.191 port 45059 ssh2
2019-12-22 07:24:49
103.55.70.82 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2019-12-22 07:40:55
51.75.29.61 attackspam
Invalid user ysp from 51.75.29.61 port 42258
2019-12-22 07:06:59
106.12.108.32 attackspam
Dec 21 23:52:55 h2177944 sshd\[27792\]: Invalid user f1 from 106.12.108.32 port 37024
Dec 21 23:52:55 h2177944 sshd\[27792\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.108.32
Dec 21 23:52:56 h2177944 sshd\[27792\]: Failed password for invalid user f1 from 106.12.108.32 port 37024 ssh2
Dec 21 23:58:28 h2177944 sshd\[28064\]: Invalid user 1qazxcde3 from 106.12.108.32 port 54754
...
2019-12-22 07:11:07
210.202.8.64 attackbots
Dec 21 18:21:33 TORMINT sshd\[11136\]: Invalid user future from 210.202.8.64
Dec 21 18:21:33 TORMINT sshd\[11136\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.202.8.64
Dec 21 18:21:34 TORMINT sshd\[11136\]: Failed password for invalid user future from 210.202.8.64 port 48131 ssh2
...
2019-12-22 07:31:36
78.170.92.19 attackspambots
Honeypot attack, port: 23, PTR: 78.170.92.19.dynamic.ttnet.com.tr.
2019-12-22 07:36:48
62.210.144.193 attackspambots
(Dec 22)  LEN=40 TTL=57 ID=61238 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 21)  LEN=40 TTL=57 ID=1093 TCP DPT=8080 WINDOW=23377 SYN 
 (Dec 20)  LEN=40 TTL=57 ID=29946 TCP DPT=8080 WINDOW=23377 SYN 
 (Dec 20)  LEN=40 TTL=57 ID=1838 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 18)  LEN=40 TTL=57 ID=49204 TCP DPT=8080 WINDOW=23377 SYN 
 (Dec 18)  LEN=40 TTL=57 ID=34969 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 18)  LEN=40 TTL=57 ID=40647 TCP DPT=8080 WINDOW=23377 SYN 
 (Dec 17)  LEN=40 TTL=57 ID=26033 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 17)  LEN=40 TTL=57 ID=1688 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 16)  LEN=40 TTL=57 ID=21524 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 16)  LEN=40 TTL=57 ID=22993 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 15)  LEN=40 TTL=57 ID=62139 TCP DPT=8080 WINDOW=9769 SYN 
 (Dec 15)  LEN=40 TTL=57 ID=5619 TCP DPT=8080 WINDOW=23377 SYN
2019-12-22 07:09:48
123.8.40.244 attack
Honeypot attack, port: 23, PTR: hn.kd.ny.adsl.
2019-12-22 07:30:38
77.235.21.147 attackbotsspam
Dec 21 23:09:34 game-panel sshd[17900]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.235.21.147
Dec 21 23:09:36 game-panel sshd[17900]: Failed password for invalid user vagina from 77.235.21.147 port 57438 ssh2
Dec 21 23:15:26 game-panel sshd[18154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.235.21.147
2019-12-22 07:42:10

最近上报的IP列表

143.70.140.29 193.95.228.32 192.119.64.112 190.186.47.224
89.70.9.154 190.137.237.108 209.130.148.120 199.138.147.251
249.223.235.155 118.137.186.242 166.14.110.36 187.162.126.105
125.93.89.103 14.160.88.202 181.87.246.236 138.56.218.184
4.145.75.181 244.250.54.52 182.185.75.71 83.6.36.188