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

城市(city): Taipei

省份(region): Taipei

国家(country): Taiwan, China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;104.199.145.185.		IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 29 08:37:34 CST 2025
;; MSG SIZE  rcvd: 108
HOST信息:
185.145.199.104.in-addr.arpa domain name pointer 185.145.199.104.bc.googleusercontent.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
185.145.199.104.in-addr.arpa	name = 185.145.199.104.bc.googleusercontent.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
197.253.124.218 attackbots
11/28/2019-01:27:18.210807 197.253.124.218 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-28 17:07:11
209.97.188.148 attackbots
Automatic report - XMLRPC Attack
2019-11-28 16:54:10
171.38.145.85 attackspambots
Port Scan
2019-11-28 16:43:15
51.89.151.214 attackspam
Nov 28 08:44:35 venus sshd\[28280\]: Invalid user ryuhei from 51.89.151.214 port 41506
Nov 28 08:44:35 venus sshd\[28280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.151.214
Nov 28 08:44:38 venus sshd\[28280\]: Failed password for invalid user ryuhei from 51.89.151.214 port 41506 ssh2
...
2019-11-28 16:58:46
212.89.28.200 attackbotsspam
Automatic report - Banned IP Access
2019-11-28 16:30:39
159.65.155.227 attackbotsspam
Nov 27 21:23:25 hanapaa sshd\[5627\]: Invalid user seeley from 159.65.155.227
Nov 27 21:23:25 hanapaa sshd\[5627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.155.227
Nov 27 21:23:27 hanapaa sshd\[5627\]: Failed password for invalid user seeley from 159.65.155.227 port 60670 ssh2
Nov 27 21:30:28 hanapaa sshd\[6157\]: Invalid user pradeep from 159.65.155.227
Nov 27 21:30:28 hanapaa sshd\[6157\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.155.227
2019-11-28 17:03:00
221.202.234.132 attack
Unauthorised access (Nov 28) SRC=221.202.234.132 LEN=40 TTL=49 ID=41571 TCP DPT=8080 WINDOW=35196 SYN 
Unauthorised access (Nov 25) SRC=221.202.234.132 LEN=40 TTL=49 ID=14706 TCP DPT=8080 WINDOW=23373 SYN
2019-11-28 16:59:59
112.85.42.174 attackbotsspam
2019-11-28T08:49:10.245036+00:00 suse sshd[20278]: User root from 112.85.42.174 not allowed because not listed in AllowUsers
2019-11-28T08:49:12.879666+00:00 suse sshd[20278]: error: PAM: Authentication failure for illegal user root from 112.85.42.174
2019-11-28T08:49:10.245036+00:00 suse sshd[20278]: User root from 112.85.42.174 not allowed because not listed in AllowUsers
2019-11-28T08:49:12.879666+00:00 suse sshd[20278]: error: PAM: Authentication failure for illegal user root from 112.85.42.174
2019-11-28T08:49:10.245036+00:00 suse sshd[20278]: User root from 112.85.42.174 not allowed because not listed in AllowUsers
2019-11-28T08:49:12.879666+00:00 suse sshd[20278]: error: PAM: Authentication failure for illegal user root from 112.85.42.174
2019-11-28T08:49:12.884325+00:00 suse sshd[20278]: Failed keyboard-interactive/pam for invalid user root from 112.85.42.174 port 63140 ssh2
...
2019-11-28 16:52:08
45.82.153.79 attack
Nov 28 09:17:46 relay postfix/smtpd\[8937\]: warning: unknown\[45.82.153.79\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 28 09:18:12 relay postfix/smtpd\[5430\]: warning: unknown\[45.82.153.79\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 28 09:20:48 relay postfix/smtpd\[10713\]: warning: unknown\[45.82.153.79\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 28 09:21:08 relay postfix/smtpd\[9814\]: warning: unknown\[45.82.153.79\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 28 09:35:49 relay postfix/smtpd\[13731\]: warning: unknown\[45.82.153.79\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-28 16:40:10
112.85.42.177 attack
2019-11-28T08:43:30.326469abusebot-3.cloudsearch.cf sshd\[2843\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.177  user=root
2019-11-28 16:57:09
107.174.148.186 attackbots
(From eric@talkwithcustomer.com) Hey,

You have a website knutsonchiropractic.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-28 16:35:04
94.43.188.136 attack
Automatic report - Port Scan Attack
2019-11-28 16:32:11
84.96.21.78 attack
2019-11-27T20:58:38.815941ts3.arvenenaske.de sshd[28902]: Invalid user rpm from 84.96.21.78 port 37308
2019-11-27T20:58:38.822716ts3.arvenenaske.de sshd[28902]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.96.21.78 user=rpm
2019-11-27T20:58:38.823646ts3.arvenenaske.de sshd[28902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.96.21.78
2019-11-27T20:58:38.815941ts3.arvenenaske.de sshd[28902]: Invalid user rpm from 84.96.21.78 port 37308
2019-11-27T20:58:40.575548ts3.arvenenaske.de sshd[28902]: Failed password for invalid user rpm from 84.96.21.78 port 37308 ssh2
2019-11-27T21:05:31.893901ts3.arvenenaske.de sshd[29009]: Invalid user palicot from 84.96.21.78 port 56212
2019-11-27T21:05:31.902082ts3.arvenenaske.de sshd[29009]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.96.21.78 user=palicot
2019-11-27T21:05:31.902988ts3.arvenenaske.de sshd[........
------------------------------
2019-11-28 16:48:57
218.92.0.170 attackbots
Nov 27 22:55:01 sachi sshd\[29198\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.170  user=root
Nov 27 22:55:04 sachi sshd\[29198\]: Failed password for root from 218.92.0.170 port 23227 ssh2
Nov 27 22:55:07 sachi sshd\[29198\]: Failed password for root from 218.92.0.170 port 23227 ssh2
Nov 27 22:55:09 sachi sshd\[29198\]: Failed password for root from 218.92.0.170 port 23227 ssh2
Nov 27 22:55:13 sachi sshd\[29198\]: Failed password for root from 218.92.0.170 port 23227 ssh2
2019-11-28 17:02:44
222.186.190.92 attackbotsspam
Nov 28 09:25:37 vps691689 sshd[10283]: Failed password for root from 222.186.190.92 port 34330 ssh2
Nov 28 09:25:41 vps691689 sshd[10283]: Failed password for root from 222.186.190.92 port 34330 ssh2
Nov 28 09:25:50 vps691689 sshd[10283]: error: maximum authentication attempts exceeded for root from 222.186.190.92 port 34330 ssh2 [preauth]
...
2019-11-28 16:27:17

最近上报的IP列表

126.150.53.161 97.69.71.14 97.73.177.159 73.98.170.212
75.88.243.54 71.235.111.147 68.72.158.217 66.217.169.152
7.109.154.197 7.58.70.203 76.38.146.243 198.197.179.191
220.38.131.167 104.102.217.130 14.153.154.240 58.127.16.76
57.36.41.107 69.101.121.84 57.135.97.60 125.249.220.51