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

城市(city): unknown

省份(region): unknown

国家(country): Germany

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;149.226.122.213.		IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 07:20:52 CST 2025
;; MSG SIZE  rcvd: 108
HOST信息:
Host 213.122.226.149.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 213.122.226.149.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
185.147.212.8 attackspambots
\[2019-12-18 04:24:54\] NOTICE\[2839\] chan_sip.c: Registration from '\' failed for '185.147.212.8:60703' - Wrong password
\[2019-12-18 04:24:54\] SECURITY\[2857\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-12-18T04:24:54.284-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="93704",SessionID="0x7f0fb4a5a908",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.147.212.8/60703",Challenge="08b9f0d7",ReceivedChallenge="08b9f0d7",ReceivedHash="e9940efdcad25d47e18018ecf6bc5cc4"
\[2019-12-18 04:25:23\] NOTICE\[2839\] chan_sip.c: Registration from '\' failed for '185.147.212.8:56724' - Wrong password
\[2019-12-18 04:25:23\] SECURITY\[2857\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-12-18T04:25:23.785-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="66333",SessionID="0x7f0fb4121288",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.1
2019-12-18 17:35:08
209.97.179.209 attackbots
Dec 17 23:01:01 php1 sshd\[32355\]: Invalid user matt from 209.97.179.209
Dec 17 23:01:01 php1 sshd\[32355\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.179.209
Dec 17 23:01:04 php1 sshd\[32355\]: Failed password for invalid user matt from 209.97.179.209 port 35272 ssh2
Dec 17 23:06:40 php1 sshd\[485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.179.209  user=root
Dec 17 23:06:42 php1 sshd\[485\]: Failed password for root from 209.97.179.209 port 44586 ssh2
2019-12-18 17:13:08
147.135.163.83 attackspambots
Dec 18 06:01:09 firewall sshd[17230]: Invalid user sorana from 147.135.163.83
Dec 18 06:01:11 firewall sshd[17230]: Failed password for invalid user sorana from 147.135.163.83 port 39982 ssh2
Dec 18 06:06:50 firewall sshd[17383]: Invalid user qtss from 147.135.163.83
...
2019-12-18 17:17:15
159.65.146.250 attack
Invalid user nital from 159.65.146.250 port 41954
2019-12-18 17:20:44
89.222.164.76 attackspambots
[portscan] Port scan
2019-12-18 17:31:33
61.94.122.175 attackspambots
Unauthorized connection attempt from IP address 61.94.122.175 on Port 445(SMB)
2019-12-18 17:18:57
119.29.12.122 attackbotsspam
Dec 18 07:41:56 vps647732 sshd[4927]: Failed password for uucp from 119.29.12.122 port 42238 ssh2
...
2019-12-18 17:28:23
209.34.25.190 attack
Unauthorised access (Dec 18) SRC=209.34.25.190 LEN=52 TTL=111 ID=17448 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-18 17:43:07
128.199.212.82 attackspam
Dec 18 10:13:11 srv01 sshd[6455]: Invalid user dan from 128.199.212.82 port 48587
Dec 18 10:13:11 srv01 sshd[6455]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.212.82
Dec 18 10:13:11 srv01 sshd[6455]: Invalid user dan from 128.199.212.82 port 48587
Dec 18 10:13:13 srv01 sshd[6455]: Failed password for invalid user dan from 128.199.212.82 port 48587 ssh2
Dec 18 10:19:12 srv01 sshd[7010]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.212.82  user=www-data
Dec 18 10:19:14 srv01 sshd[7010]: Failed password for www-data from 128.199.212.82 port 51765 ssh2
...
2019-12-18 17:39:25
113.190.232.84 attackbotsspam
Unauthorized connection attempt detected from IP address 113.190.232.84 to port 1433
2019-12-18 17:43:57
118.89.221.77 attack
Dec 16 10:23:05 h2022099 sshd[30517]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.221.77  user=mysql
Dec 16 10:23:07 h2022099 sshd[30517]: Failed password for mysql from 118.89.221.77 port 38428 ssh2
Dec 16 10:23:07 h2022099 sshd[30517]: Received disconnect from 118.89.221.77: 11: Bye Bye [preauth]
Dec 16 10:58:15 h2022099 sshd[7214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.221.77  user=backup
Dec 16 10:58:17 h2022099 sshd[7214]: Failed password for backup from 118.89.221.77 port 60546 ssh2
Dec 16 10:58:17 h2022099 sshd[7214]: Received disconnect from 118.89.221.77: 11: Bye Bye [preauth]
Dec 16 11:04:34 h2022099 sshd[8569]: Invalid user miso from 118.89.221.77
Dec 16 11:04:34 h2022099 sshd[8569]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.221.77 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=118.89.22
2019-12-18 17:16:47
49.88.112.63 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-12-18 17:40:50
178.62.54.233 attackspam
2019-12-18T08:08:35.529664abusebot-2.cloudsearch.cf sshd\[17616\]: Invalid user super from 178.62.54.233 port 57510
2019-12-18T08:08:35.536508abusebot-2.cloudsearch.cf sshd\[17616\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.54.233
2019-12-18T08:08:37.940029abusebot-2.cloudsearch.cf sshd\[17616\]: Failed password for invalid user super from 178.62.54.233 port 57510 ssh2
2019-12-18T08:13:18.075301abusebot-2.cloudsearch.cf sshd\[17621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.54.233  user=ftp
2019-12-18 17:15:04
202.65.135.91 attackbots
Dec 18 09:26:44 web8 sshd\[20004\]: Invalid user jh from 202.65.135.91
Dec 18 09:26:44 web8 sshd\[20004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.65.135.91
Dec 18 09:26:45 web8 sshd\[20004\]: Failed password for invalid user jh from 202.65.135.91 port 43882 ssh2
Dec 18 09:32:57 web8 sshd\[23031\]: Invalid user hhh45688 from 202.65.135.91
Dec 18 09:32:57 web8 sshd\[23031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.65.135.91
2019-12-18 17:35:53
177.94.225.207 attack
Dec 18 02:53:04 srv1 sshd[23710]: Address 177.94.225.207 maps to 177-94-225-207.dsl.telesp.net.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 18 02:53:04 srv1 sshd[23710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.94.225.207  user=ftp
Dec 18 02:53:07 srv1 sshd[23710]: Failed password for ftp from 177.94.225.207 port 33408 ssh2
Dec 18 02:53:07 srv1 sshd[23711]: Received disconnect from 177.94.225.207: 11: Bye Bye
Dec 18 04:01:46 srv1 sshd[26454]: Address 177.94.225.207 maps to 177-94-225-207.dsl.telesp.net.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 18 04:01:46 srv1 sshd[26454]: Invalid user kursa from 177.94.225.207
Dec 18 04:01:46 srv1 sshd[26454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.94.225.207 
Dec 18 04:01:48 srv1 sshd[26454]: Failed password for invalid user kursa from 177.94.225.207 port 48960 s........
-------------------------------
2019-12-18 17:43:34

最近上报的IP列表

66.192.84.148 37.69.177.104 97.226.154.108 92.40.99.14
201.84.239.227 79.163.20.227 232.125.133.137 233.230.17.69
128.103.14.148 129.239.234.130 132.248.249.157 13.157.172.167
91.9.208.104 44.72.136.169 86.67.220.75 93.189.114.89
240.114.253.6 41.219.76.12 28.188.253.128 46.101.64.0