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

城市(city): unknown

省份(region): unknown

国家(country): United States

运营商(isp): AT&T

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

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

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

;; Query time: 35 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Sep 15 00:32:38 CST 2019
;; MSG SIZE  rcvd: 117
HOST信息:
196.56.134.12.in-addr.arpa domain name pointer 196.mui56.dytn.cgcil02r18.dsl.att.net.
NSLOOKUP信息:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
196.56.134.12.in-addr.arpa	name = 196.mui56.dytn.cgcil02r18.dsl.att.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
36.89.251.105 attack
36.89.251.105 - - [02/Aug/2020:21:42:08 +0200] "GET /wp-login.php HTTP/1.1" 200 6310 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
36.89.251.105 - - [02/Aug/2020:21:42:12 +0200] "POST /wp-login.php HTTP/1.1" 200 6561 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
36.89.251.105 - - [02/Aug/2020:21:42:14 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-08-03 04:18:11
198.211.96.122 attackbotsspam
DATE:2020-08-02 14:03:33, IP:198.211.96.122, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2020-08-03 04:00:43
138.68.148.177 attackspam
Aug  2 13:48:42 vpn01 sshd[1565]: Failed password for root from 138.68.148.177 port 45518 ssh2
...
2020-08-03 04:25:54
192.144.210.27 attack
Bruteforce detected by fail2ban
2020-08-03 04:16:31
109.168.219.0 attack
port scan and connect, tcp 23 (telnet)
2020-08-03 04:01:25
121.201.95.66 attackspam
Aug  2 20:16:37 srv-ubuntu-dev3 sshd[38549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.201.95.66  user=root
Aug  2 20:16:39 srv-ubuntu-dev3 sshd[38549]: Failed password for root from 121.201.95.66 port 42411 ssh2
Aug  2 20:18:24 srv-ubuntu-dev3 sshd[38839]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.201.95.66  user=root
Aug  2 20:18:26 srv-ubuntu-dev3 sshd[38839]: Failed password for root from 121.201.95.66 port 10794 ssh2
Aug  2 20:20:18 srv-ubuntu-dev3 sshd[39046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.201.95.66  user=root
Aug  2 20:20:20 srv-ubuntu-dev3 sshd[39046]: Failed password for root from 121.201.95.66 port 35680 ssh2
Aug  2 20:22:09 srv-ubuntu-dev3 sshd[39279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.201.95.66  user=root
Aug  2 20:22:12 srv-ubuntu-dev3 sshd[39279]: Failed p
...
2020-08-03 04:13:59
66.152.179.100 attack
321/tcp
[2020-08-02]1pkt
2020-08-03 03:59:24
213.21.29.23 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-08-03 04:24:02
61.220.101.99 attackbots
445/tcp 1433/tcp...
[2020-06-03/08-02]12pkt,2pt.(tcp)
2020-08-03 04:09:54
36.237.67.172 attackbots
20/8/2@08:03:31: FAIL: Alarm-Network address from=36.237.67.172
20/8/2@08:03:31: FAIL: Alarm-Network address from=36.237.67.172
...
2020-08-03 04:01:41
112.64.33.38 attackspambots
Aug  2 22:02:10 serwer sshd\[20593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.33.38  user=root
Aug  2 22:02:11 serwer sshd\[20593\]: Failed password for root from 112.64.33.38 port 56195 ssh2
Aug  2 22:10:04 serwer sshd\[21594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.33.38  user=root
...
2020-08-03 04:13:32
106.75.67.48 attackspam
Aug  2 18:00:35 vlre-nyc-1 sshd\[3209\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.67.48  user=root
Aug  2 18:00:36 vlre-nyc-1 sshd\[3209\]: Failed password for root from 106.75.67.48 port 45997 ssh2
Aug  2 18:05:05 vlre-nyc-1 sshd\[3293\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.67.48  user=root
Aug  2 18:05:06 vlre-nyc-1 sshd\[3293\]: Failed password for root from 106.75.67.48 port 47735 ssh2
Aug  2 18:09:35 vlre-nyc-1 sshd\[3386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.67.48  user=root
...
2020-08-03 04:11:27
212.64.66.28 attackbots
Trolling for resource vulnerabilities
2020-08-03 04:10:49
116.90.230.243 attack
2-8-2020 13:56:10	Unauthorized connection attempt (Brute-Force).
2-8-2020 13:56:10	Connection from IP address: 116.90.230.243 on port: 587


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=116.90.230.243
2020-08-03 04:11:43
176.164.103.39 attackbots
Lines containing failures of 176.164.103.39 (max 1000)
Aug  2 13:54:52 srv sshd[204246]: Invalid user pi from 176.164.103.39 port 48472
Aug  2 13:54:52 srv sshd[204248]: Invalid user pi from 176.164.103.39 port 48474
Aug  2 13:54:52 srv sshd[204248]: Connection closed by invalid user pi 176.164.103.39 port 48474 [preauth]
Aug  2 13:54:52 srv sshd[204246]: Connection closed by invalid user pi 176.164.103.39 port 48472 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=176.164.103.39
2020-08-03 04:03:28

最近上报的IP列表

178.2.240.87 36.90.178.233 98.165.144.237 97.152.61.167
126.193.14.179 52.74.247.50 164.116.24.250 125.43.110.7
186.54.170.143 69.13.46.39 66.69.18.74 172.4.69.139
146.200.208.156 113.251.29.243 150.65.105.58 222.141.228.231
47.243.164.42 39.60.113.173 114.117.95.113 78.43.59.106