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

城市(city): Xi'an

省份(region): Shaanxi

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

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

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

;; Query time: 94 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 09:19:33 CST 2020
;; MSG SIZE  rcvd: 119
HOST信息:
Host 148.219.139.113.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 148.219.139.113.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
58.64.21.92 attackbots
Jul  7 19:14:36 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:36 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:42 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:42 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:48 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:49 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:53 aragorn pop3d: LOGIN FAILED, user=admin@131.37, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:53 aragorn pop3d: LOGIN FAILED, user=admin@131.36, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:54 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
Jul  7 19:14:55 aragorn pop3d: LOGIN FAILED, user=admin@typhon.ca, ip=\[::ffff:58.64.21.92\]\
2019-07-08 07:21:18
49.69.35.169 attackspam
Jul  2 20:38:45 pl3server sshd[2121851]: Invalid user admin from 49.69.35.169
Jul  2 20:38:45 pl3server sshd[2121851]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.69.35.169
Jul  2 20:38:47 pl3server sshd[2121851]: Failed password for invalid user admin from 49.69.35.169 port 59185 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.69.35.169
2019-07-08 07:45:49
94.23.145.156 attackspambots
Blocked range because of multiple attacks in the past. @ 2019-07-08T01:09:30+02:00.
2019-07-08 07:20:14
51.255.219.56 attackspambots
Blocked range because of multiple attacks in the past. @ 2019-07-08T01:00:41+02:00.
2019-07-08 07:18:02
91.207.175.154 attackspam
" "
2019-07-08 07:44:03
139.180.227.127 attackbots
Looking for resource vulnerabilities
2019-07-08 07:45:29
77.88.5.49 attack
EventTime:Mon Jul 8 09:14:29 AEST 2019,Protocol:UDP,VendorEventCode:RT_FLOW_SESSION_DENY,TargetPort:53,SourceIP:77.88.5.49,SourcePort:59591
2019-07-08 07:22:07
178.140.140.13 attack
Jul  1 23:17:26 m3061 sshd[18069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=broadband-178-140-140-13.ip.moscow.rt.ru  user=r.r
Jul  1 23:17:28 m3061 sshd[18069]: Failed password for r.r from 178.140.140.13 port 59506 ssh2
Jul  1 23:17:30 m3061 sshd[18069]: Failed password for r.r from 178.140.140.13 port 59506 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=178.140.140.13
2019-07-08 07:27:57
134.255.233.10 attackspam
Jul  7 15:10:54 tux postfix/smtpd[17275]: warning: hostname vps-zap428766-2.zap-srv.com does not resolve to address 134.255.233.10: Name or service not known
Jul  7 15:10:54 tux postfix/smtpd[17275]: connect from unknown[134.255.233.10]
Jul  7 15:10:54 tux postfix/smtpd[17275]: NOQUEUE: reject: RCPT from unknown[134.255.233.10]: 554 5.7.1 Service unavailable; Client host [134.255.233.10] blocked using ix.dnsbl.xxxxxx.net; Your e-mail service was detected by spam.over.port25.me (NiX Spam) as spamming at Sun, 07 Jul 2019 15:08:55 +0200. Your admin should vishostname hxxp://www.dnsbl.xxxxxx.net/lookup.php?value=134.255.233.10; from=x@x helo=
Jul  7 15:10:54 tux postfix/smtpd[17653]: warning: hostname vps-zap428766-2.zap-srv.com does not resolve to address 134.255.233.10: Name or service not known
Jul  7 15:10:54 tux postfix/smtpd[17653]: connect from unknown[134.255.233.10]
Jul  7 15:10:54 tux postfix/smtpd[17275]: disconnect from unknown[134.255.233.10]
J........
-------------------------------
2019-07-08 07:16:59
212.224.108.130 attackspambots
2019-07-07T23:14:30.093271abusebot-4.cloudsearch.cf sshd\[20953\]: Invalid user admin from 212.224.108.130 port 58539
2019-07-08 07:35:35
117.1.94.200 attackspam
Caught in portsentry honeypot
2019-07-08 07:31:20
134.209.157.64 attackbots
Triggered by Fail2Ban
2019-07-08 07:26:12
191.53.249.120 attack
smtp auth brute force
2019-07-08 07:17:42
121.23.185.101 attackbots
Telnet Server BruteForce Attack
2019-07-08 07:08:03
175.138.159.233 attackspambots
Invalid user tomcat from 175.138.159.233 port 47890
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.138.159.233
Failed password for invalid user tomcat from 175.138.159.233 port 47890 ssh2
Invalid user sr from 175.138.159.233 port 37983
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.138.159.233
2019-07-08 07:13:28

最近上报的IP列表

177.92.244.158 122.220.253.79 208.221.69.191 168.205.192.111
197.176.188.90 108.29.122.200 202.110.184.42 210.152.58.184
143.255.52.150 113.251.22.219 186.183.62.193 223.156.224.216
241.220.167.40 16.31.199.9 253.129.9.254 103.58.115.42
12.158.170.141 38.68.80.95 66.222.58.154 228.255.5.110