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

城市(city): unknown

省份(region): unknown

国家(country): None

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;213.47.147.104.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 01:43:29 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
104.147.47.213.in-addr.arpa domain name pointer 213-47-147-104.cable.dynamic.surfer.at.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.147.47.213.in-addr.arpa	name = 213-47-147-104.cable.dynamic.surfer.at.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
192.99.57.32 attackbots
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:45:49,311 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:04:25,251 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:34:15,337 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:45:49,311 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:04:25,251 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:34:15,337 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850
2019-11-01 03:30:34
18.189.6.233 attackbots
Oct 31 22:03:57 server sshd\[8496\]: Invalid user xx from 18.189.6.233
Oct 31 22:03:57 server sshd\[8496\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-189-6-233.us-east-2.compute.amazonaws.com 
Oct 31 22:03:59 server sshd\[8496\]: Failed password for invalid user xx from 18.189.6.233 port 41796 ssh2
Oct 31 22:17:45 server sshd\[11601\]: Invalid user viorel from 18.189.6.233
Oct 31 22:17:45 server sshd\[11601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-189-6-233.us-east-2.compute.amazonaws.com 
...
2019-11-01 03:35:02
41.211.116.32 attack
Oct 31 12:25:59 thevastnessof sshd[22752]: Failed password for invalid user cjs962129 from 41.211.116.32 port 52196 ssh2
...
2019-11-01 03:56:51
92.63.194.70 attackspambots
Unauthorized connection attempt from IP address 92.63.194.70 on Port 3389(RDP)
2019-11-01 03:52:12
188.162.199.42 attackspam
failed_logins
2019-11-01 03:35:55
27.128.226.176 attackspam
Oct 28 06:35:16 newdogma sshd[28813]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.128.226.176  user=r.r
Oct 28 06:35:17 newdogma sshd[28813]: Failed password for r.r from 27.128.226.176 port 48378 ssh2
Oct 28 06:35:17 newdogma sshd[28813]: Received disconnect from 27.128.226.176 port 48378:11: Bye Bye [preauth]
Oct 28 06:35:17 newdogma sshd[28813]: Disconnected from 27.128.226.176 port 48378 [preauth]
Oct 28 07:03:04 newdogma sshd[28924]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.128.226.176  user=r.r
Oct 28 07:03:07 newdogma sshd[28924]: Failed password for r.r from 27.128.226.176 port 36630 ssh2
Oct 28 07:03:07 newdogma sshd[28924]: Received disconnect from 27.128.226.176 port 36630:11: Bye Bye [preauth]
Oct 28 07:03:07 newdogma sshd[28924]: Disconnected from 27.128.226.176 port 36630 [preauth]
Oct 28 07:09:07 newdogma sshd[28997]: Invalid user hercul from 27.128.226.176 po........
-------------------------------
2019-11-01 03:29:34
52.164.211.22 attackspambots
SSH Brute Force, server-1 sshd[24127]: Failed password for root from 52.164.211.22 port 40352 ssh2
2019-11-01 03:50:31
101.230.238.32 attack
Lines containing failures of 101.230.238.32
Oct 28 08:38:15 shared10 sshd[11855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.238.32  user=r.r
Oct 28 08:38:17 shared10 sshd[11855]: Failed password for r.r from 101.230.238.32 port 40722 ssh2
Oct 28 08:38:18 shared10 sshd[11855]: Received disconnect from 101.230.238.32 port 40722:11: Bye Bye [preauth]
Oct 28 08:38:18 shared10 sshd[11855]: Disconnected from authenticating user r.r 101.230.238.32 port 40722 [preauth]
Oct 28 09:02:20 shared10 sshd[19793]: Invalid user hattori from 101.230.238.32 port 51834
Oct 28 09:02:20 shared10 sshd[19793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.238.32
Oct 28 09:02:22 shared10 sshd[19793]: Failed password for invalid user hattori from 101.230.238.32 port 51834 ssh2
Oct 28 09:02:22 shared10 sshd[19793]: Received disconnect from 101.230.238.32 port 51834:11: Bye Bye [preauth]
Oct 28 0........
------------------------------
2019-11-01 03:33:38
92.127.247.108 attackbotsspam
Chat Spam
2019-11-01 03:55:56
117.132.14.250 attack
Oct 31 15:49:26 vpn01 sshd[4718]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.132.14.250
Oct 31 15:49:27 vpn01 sshd[4718]: Failed password for invalid user gua from 117.132.14.250 port 35816 ssh2
...
2019-11-01 03:32:49
167.71.141.204 attackspam
PostgreSQL port 5432
2019-11-01 03:47:37
211.169.249.156 attackbots
Oct 31 21:37:58 server sshd\[2863\]: Invalid user k from 211.169.249.156
Oct 31 21:37:58 server sshd\[2863\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.156 
Oct 31 21:38:00 server sshd\[2863\]: Failed password for invalid user k from 211.169.249.156 port 50240 ssh2
Oct 31 21:58:55 server sshd\[7422\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.156  user=root
Oct 31 21:58:57 server sshd\[7422\]: Failed password for root from 211.169.249.156 port 35450 ssh2
...
2019-11-01 03:26:43
220.76.205.178 attack
Oct 31 20:41:20 MainVPS sshd[28691]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178  user=root
Oct 31 20:41:22 MainVPS sshd[28691]: Failed password for root from 220.76.205.178 port 45559 ssh2
Oct 31 20:45:30 MainVPS sshd[29005]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178  user=root
Oct 31 20:45:32 MainVPS sshd[29005]: Failed password for root from 220.76.205.178 port 36760 ssh2
Oct 31 20:49:48 MainVPS sshd[29317]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178  user=root
Oct 31 20:49:50 MainVPS sshd[29317]: Failed password for root from 220.76.205.178 port 56190 ssh2
...
2019-11-01 04:00:38
168.128.86.35 attack
2019-10-31T11:58:18.227509abusebot-5.cloudsearch.cf sshd\[31880\]: Invalid user freedom from 168.128.86.35 port 52228
2019-11-01 03:39:06
174.254.194.96 attackspam
Port Scan: TCP/443
2019-11-01 03:40:14

最近上报的IP列表

213.45.83.251 213.5.182.115 213.5.180.151 213.5.65.8
213.5.56.43 213.5.70.57 213.5.71.23 213.5.47.250
213.5.71.65 213.5.71.251 213.5.80.247 213.52.128.182
213.5.79.23 213.5.65.7 213.52.129.125 213.52.128.19
213.52.132.42 213.52.133.246 213.52.130.247 213.52.133.247