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

城市(city): unknown

省份(region): unknown

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

;; QUESTION SECTION:
;104.195.5.134.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 13:53:59 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 134.5.195.104.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.5.195.104.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
42.48.104.45 attackbotsspam
" "
2019-07-27 10:56:08
49.234.106.172 attackbotsspam
Jul 27 03:16:06 localhost sshd\[44362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.106.172  user=root
Jul 27 03:16:08 localhost sshd\[44362\]: Failed password for root from 49.234.106.172 port 41938 ssh2
Jul 27 03:20:40 localhost sshd\[44513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.106.172  user=root
Jul 27 03:20:42 localhost sshd\[44513\]: Failed password for root from 49.234.106.172 port 56932 ssh2
Jul 27 03:25:11 localhost sshd\[44644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.106.172  user=root
...
2019-07-27 11:34:30
128.0.140.236 attackspam
Jul 26 22:07:55 vps647732 sshd[6253]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.0.140.236
Jul 26 22:07:57 vps647732 sshd[6253]: Failed password for invalid user ubnt from 128.0.140.236 port 39722 ssh2
...
2019-07-27 10:57:11
176.109.235.193 attack
" "
2019-07-27 11:06:12
209.97.161.162 attack
Invalid user applmgr from 209.97.161.162 port 33936
2019-07-27 10:42:40
206.189.145.152 attack
Jul 27 02:48:53 marvibiene sshd[9656]: Invalid user nagios from 206.189.145.152 port 40745
Jul 27 02:48:53 marvibiene sshd[9656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.145.152
Jul 27 02:48:53 marvibiene sshd[9656]: Invalid user nagios from 206.189.145.152 port 40745
Jul 27 02:48:55 marvibiene sshd[9656]: Failed password for invalid user nagios from 206.189.145.152 port 40745 ssh2
...
2019-07-27 11:16:15
129.154.67.65 attackspam
frenzy
2019-07-27 11:21:51
109.202.0.14 attack
Jul 27 04:39:08 eventyay sshd[14652]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.202.0.14
Jul 27 04:39:10 eventyay sshd[14652]: Failed password for invalid user wocloud from 109.202.0.14 port 37992 ssh2
Jul 27 04:43:57 eventyay sshd[15898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.202.0.14
...
2019-07-27 10:58:15
101.81.125.26 attack
Automatic report - Banned IP Access
2019-07-27 11:28:26
52.151.38.54 attackspambots
Jul 27 05:39:47 server sshd\[12552\]: Invalid user Galax@8800 from 52.151.38.54 port 48330
Jul 27 05:39:47 server sshd\[12552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.151.38.54
Jul 27 05:39:50 server sshd\[12552\]: Failed password for invalid user Galax@8800 from 52.151.38.54 port 48330 ssh2
Jul 27 05:48:50 server sshd\[14401\]: Invalid user bio035!@\# from 52.151.38.54 port 43932
Jul 27 05:48:50 server sshd\[14401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.151.38.54
2019-07-27 11:12:09
220.136.48.242 attackbotsspam
Jul 26 07:52:21 localhost kernel: [15386134.298660] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.136.48.242 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=19765 PROTO=TCP SPT=15491 DPT=37215 WINDOW=17652 RES=0x00 SYN URGP=0 
Jul 26 07:52:21 localhost kernel: [15386134.298684] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.136.48.242 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=19765 PROTO=TCP SPT=15491 DPT=37215 SEQ=758669438 ACK=0 WINDOW=17652 RES=0x00 SYN URGP=0 
Jul 26 15:40:31 localhost kernel: [15414224.440693] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.136.48.242 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=21380 PROTO=TCP SPT=15491 DPT=37215 WINDOW=17652 RES=0x00 SYN URGP=0 
Jul 26 15:40:31 localhost kernel: [15414224.440701] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=220.136.48.242 DST=[mungedIP2] LEN=40 TOS
2019-07-27 11:15:17
172.93.192.212 attackspambots
(From eric@talkwithcustomer.com) Hello strawbridgechiropractic.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 strawbridgechiropractic.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 strawbridgechiropractic.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 Perf
2019-07-27 10:56:41
103.113.105.11 attackbotsspam
Jul 26 20:41:59 localhost sshd\[27061\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.113.105.11  user=root
Jul 26 20:42:01 localhost sshd\[27061\]: Failed password for root from 103.113.105.11 port 44582 ssh2
...
2019-07-27 10:41:52
51.38.231.36 attackbotsspam
Invalid user root1 from 51.38.231.36 port 42792
2019-07-27 11:33:09
88.123.13.140 attack
Automatic report - Port Scan Attack
2019-07-27 11:29:20

最近上报的IP列表

105.112.83.55 104.195.5.136 105.112.84.106 104.196.11.185
104.196.119.126 105.112.84.108 104.196.120.147 104.196.126.195
104.196.132.107 104.196.137.180 104.196.138.215 104.196.143.196
104.196.149.216 104.196.148.90 104.196.134.17 104.196.154.229
105.112.84.118 104.196.159.14 104.196.162.236 104.196.17.252