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

城市(city): unknown

省份(region): unknown

国家(country): United Kingdom of Great Britain and Northern Ireland (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;5.45.49.134.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 00:06:14 CST 2025
;; MSG SIZE  rcvd: 104
HOST信息:
Host 134.49.45.5.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.49.45.5.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
198.98.49.8 attack
Triggered by Fail2Ban at Vostok web server
2019-08-09 08:29:37
36.71.246.170 attackspambots
WordPress wp-login brute force :: 36.71.246.170 0.176 BYPASS [09/Aug/2019:07:53:09  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-08-09 08:06:39
46.166.151.47 attackspam
\[2019-08-08 19:40:14\] SECURITY\[2326\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-08-08T19:40:14.362-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="01246406820923",SessionID="0x7ff4d0160998",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.151.47/58181",ACLName="no_extension_match"
\[2019-08-08 19:45:42\] SECURITY\[2326\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-08-08T19:45:42.432-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="001546812410249",SessionID="0x7ff4d0160998",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.151.47/53510",ACLName="no_extension_match"
\[2019-08-08 19:49:22\] SECURITY\[2326\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-08-08T19:49:22.933-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="46406829453",SessionID="0x7ff4d0160998",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.151.47/60644",ACLName="no_extensio
2019-08-09 07:56:08
106.13.33.181 attackspambots
Aug  9 01:31:48 localhost sshd\[3667\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.33.181  user=root
Aug  9 01:31:50 localhost sshd\[3667\]: Failed password for root from 106.13.33.181 port 56950 ssh2
Aug  9 01:38:14 localhost sshd\[3860\]: Invalid user sysomc from 106.13.33.181
Aug  9 01:38:14 localhost sshd\[3860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.33.181
Aug  9 01:38:16 localhost sshd\[3860\]: Failed password for invalid user sysomc from 106.13.33.181 port 44972 ssh2
...
2019-08-09 08:21:35
185.49.26.109 attack
Aug  8 21:53:21 system,error,critical: login failure for user admin from 185.49.26.109 via telnet
Aug  8 21:53:23 system,error,critical: login failure for user root from 185.49.26.109 via telnet
Aug  8 21:53:24 system,error,critical: login failure for user root from 185.49.26.109 via telnet
Aug  8 21:53:29 system,error,critical: login failure for user 666666 from 185.49.26.109 via telnet
Aug  8 21:53:30 system,error,critical: login failure for user root from 185.49.26.109 via telnet
Aug  8 21:53:32 system,error,critical: login failure for user root from 185.49.26.109 via telnet
Aug  8 21:53:37 system,error,critical: login failure for user admin from 185.49.26.109 via telnet
Aug  8 21:53:38 system,error,critical: login failure for user root from 185.49.26.109 via telnet
Aug  8 21:53:40 system,error,critical: login failure for user supervisor from 185.49.26.109 via telnet
Aug  8 21:53:43 system,error,critical: login failure for user root from 185.49.26.109 via telnet
2019-08-09 07:48:55
218.92.0.154 attackspambots
Aug  8 23:53:36 dedicated sshd[31803]: Failed password for root from 218.92.0.154 port 42561 ssh2
Aug  8 23:53:39 dedicated sshd[31803]: Failed password for root from 218.92.0.154 port 42561 ssh2
Aug  8 23:53:41 dedicated sshd[31803]: Failed password for root from 218.92.0.154 port 42561 ssh2
Aug  8 23:53:44 dedicated sshd[31803]: Failed password for root from 218.92.0.154 port 42561 ssh2
Aug  8 23:53:47 dedicated sshd[31803]: Failed password for root from 218.92.0.154 port 42561 ssh2
2019-08-09 07:47:39
92.43.24.226 attackbotsspam
fire
2019-08-09 08:04:16
87.180.70.184 attackspam
Invalid user azure from 87.180.70.184 port 37354
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.180.70.184
Failed password for invalid user azure from 87.180.70.184 port 37354 ssh2
Invalid user matrix from 87.180.70.184 port 34008
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.180.70.184
2019-08-09 08:05:01
104.250.166.43 attackbotsspam
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-08-08 21:35:15,907 INFO [amun_request_handler] PortScan Detected on Port: 445 (104.250.166.43)
2019-08-09 07:49:56
178.128.52.162 attack
2019-08-09T01:50:20.852915centos sshd\[2725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.52.162  user=root
2019-08-09T01:50:22.333407centos sshd\[2725\]: Failed password for root from 178.128.52.162 port 55648 ssh2
2019-08-09T01:56:16.763140centos sshd\[2860\]: Invalid user legal3 from 178.128.52.162 port 60446
2019-08-09 07:58:43
37.187.3.60 attackspambots
Aug  9 03:15:32 yabzik sshd[14622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.3.60
Aug  9 03:15:33 yabzik sshd[14622]: Failed password for invalid user akash from 37.187.3.60 port 53760 ssh2
Aug  9 03:20:48 yabzik sshd[16291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.3.60
2019-08-09 08:30:56
51.83.72.243 attackbots
Automatic report - Banned IP Access
2019-08-09 08:06:22
94.220.213.254 attack
fire
2019-08-09 08:02:54
211.24.79.26 attackspam
Aug  8 23:53:15 vpn01 sshd\[17238\]: Invalid user user from 211.24.79.26
Aug  8 23:53:15 vpn01 sshd\[17238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.24.79.26
Aug  8 23:53:16 vpn01 sshd\[17238\]: Failed password for invalid user user from 211.24.79.26 port 48494 ssh2
2019-08-09 08:00:29
182.219.172.224 attackbotsspam
Aug  7 19:15:23 tuxlinux sshd[8111]: Invalid user appli from 182.219.172.224 port 47684
Aug  7 19:15:23 tuxlinux sshd[8111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.219.172.224 
Aug  7 19:15:23 tuxlinux sshd[8111]: Invalid user appli from 182.219.172.224 port 47684
Aug  7 19:15:23 tuxlinux sshd[8111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.219.172.224 
Aug  7 19:15:23 tuxlinux sshd[8111]: Invalid user appli from 182.219.172.224 port 47684
Aug  7 19:15:23 tuxlinux sshd[8111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.219.172.224 
Aug  7 19:15:25 tuxlinux sshd[8111]: Failed password for invalid user appli from 182.219.172.224 port 47684 ssh2
...
2019-08-09 08:10:03

最近上报的IP列表

74.90.122.173 64.48.22.93 116.81.175.52 174.9.218.100
213.172.65.51 116.81.87.171 203.174.86.61 142.67.91.104
135.81.60.20 237.12.219.140 13.70.151.30 164.4.13.193
44.50.117.209 132.95.74.225 34.220.37.101 7.53.223.191
60.163.168.249 164.10.94.156 94.228.6.184 237.72.187.182