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

城市(city): Omitama

省份(region): Ibaraki

国家(country): Japan

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

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

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

;; Query time: 106 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 01 02:45:02 CST 2019
;; MSG SIZE  rcvd: 118
HOST信息:
145.140.214.61.in-addr.arpa domain name pointer p1616145-ipngn6701akatuka.ibaraki.ocn.ne.jp.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
145.140.214.61.in-addr.arpa	name = p1616145-ipngn6701akatuka.ibaraki.ocn.ne.jp.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
122.59.181.52 attackspam
Brute force attack against VPN service
2020-04-04 18:43:47
51.254.143.190 attack
[ssh] SSH attack
2020-04-04 19:25:21
192.3.41.204 attack
Automatic report - Malicious Script Upload
2020-04-04 19:00:58
165.22.251.83 attackbots
2020-04-03 UTC: (53x) - ,admin,alan,jw,luojinhao,nproc(22x),root(22x),sjkx,student7,t,wrchang
2020-04-04 19:04:39
103.129.223.98 attackbotsspam
2020-04-04T08:04:49.743770abusebot.cloudsearch.cf sshd[3045]: Invalid user jinheon from 103.129.223.98 port 46490
2020-04-04T08:04:49.750959abusebot.cloudsearch.cf sshd[3045]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.129.223.98
2020-04-04T08:04:49.743770abusebot.cloudsearch.cf sshd[3045]: Invalid user jinheon from 103.129.223.98 port 46490
2020-04-04T08:04:52.368611abusebot.cloudsearch.cf sshd[3045]: Failed password for invalid user jinheon from 103.129.223.98 port 46490 ssh2
2020-04-04T08:07:25.002110abusebot.cloudsearch.cf sshd[3237]: Invalid user hc from 103.129.223.98 port 56330
2020-04-04T08:07:25.008294abusebot.cloudsearch.cf sshd[3237]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.129.223.98
2020-04-04T08:07:25.002110abusebot.cloudsearch.cf sshd[3237]: Invalid user hc from 103.129.223.98 port 56330
2020-04-04T08:07:26.709999abusebot.cloudsearch.cf sshd[3237]: Failed password for inv
...
2020-04-04 19:08:57
122.155.11.89 attackbots
Apr  4 08:42:54 server sshd\[19397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.11.89  user=root
Apr  4 08:42:56 server sshd\[19397\]: Failed password for root from 122.155.11.89 port 37044 ssh2
Apr  4 08:58:51 server sshd\[23373\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.11.89  user=root
Apr  4 08:58:53 server sshd\[23373\]: Failed password for root from 122.155.11.89 port 33080 ssh2
Apr  4 09:03:40 server sshd\[24640\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.11.89  user=root
...
2020-04-04 19:20:22
125.132.73.14 attackspambots
Invalid user linkage from 125.132.73.14 port 47374
2020-04-04 19:24:13
54.39.138.249 attackbots
Apr  4 10:40:52 powerpi2 sshd[9087]: Failed password for invalid user mysql from 54.39.138.249 port 48884 ssh2
Apr  4 10:46:16 powerpi2 sshd[9552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.138.249  user=root
Apr  4 10:46:18 powerpi2 sshd[9552]: Failed password for root from 54.39.138.249 port 60230 ssh2
...
2020-04-04 19:09:53
27.34.47.87 attackbots
SSH brutforce
2020-04-04 18:44:49
179.185.89.232 attackspam
2020-04-04T10:58:28.773528shield sshd\[32652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.185.89.232  user=root
2020-04-04T10:58:30.739763shield sshd\[32652\]: Failed password for root from 179.185.89.232 port 42328 ssh2
2020-04-04T11:01:24.081061shield sshd\[560\]: Invalid user pumin from 179.185.89.232 port 51678
2020-04-04T11:01:24.085424shield sshd\[560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.185.89.232
2020-04-04T11:01:26.212395shield sshd\[560\]: Failed password for invalid user pumin from 179.185.89.232 port 51678 ssh2
2020-04-04 19:13:41
14.172.246.199 attackbots
/wp-admin/admin-ajax.php?nd_bo…   etc etc etc
2020-04-04 19:13:20
106.12.220.84 attackspambots
Apr  4 12:06:55 nextcloud sshd\[19539\]: Invalid user tb from 106.12.220.84
Apr  4 12:06:55 nextcloud sshd\[19539\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.220.84
Apr  4 12:06:57 nextcloud sshd\[19539\]: Failed password for invalid user tb from 106.12.220.84 port 35288 ssh2
2020-04-04 19:03:29
91.121.135.79 attackspambots
Brute force attempts on SSH.
2020-04-04 18:56:54
220.247.237.230 attackspambots
Apr  4 13:14:27 tuxlinux sshd[4859]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.247.237.230  user=root
Apr  4 13:14:29 tuxlinux sshd[4859]: Failed password for root from 220.247.237.230 port 47964 ssh2
Apr  4 13:14:27 tuxlinux sshd[4859]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.247.237.230  user=root
Apr  4 13:14:29 tuxlinux sshd[4859]: Failed password for root from 220.247.237.230 port 47964 ssh2
...
2020-04-04 19:22:29
104.199.216.0 attackbots
"XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES:
2020-04-04 19:11:22

最近上报的IP列表

114.228.201.57 91.150.127.127 67.58.119.253 52.152.149.236
110.189.81.168 98.82.119.51 198.189.85.168 27.75.29.218
102.87.192.174 63.81.87.112 100.245.200.72 70.50.72.224
183.203.249.185 49.207.100.177 198.13.110.16 190.159.192.248
35.247.48.61 201.111.37.230 166.195.147.110 129.130.86.109