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

城市(city): unknown

省份(region): unknown

国家(country): IANA Special-Purpose Address

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;241.29.157.12.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 07 12:34:14 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 12.157.29.241.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 12.157.29.241.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
111.206.198.53 attack
Bad bot/spoofed identity
2020-04-22 20:32:52
113.193.243.35 attackbotsspam
$f2bV_matches
2020-04-22 20:59:45
173.44.164.14 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found millenniumchiro.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software tha
2020-04-22 20:51:52
54.39.138.246 attackspambots
"fail2ban match"
2020-04-22 21:10:18
113.78.64.97 attackspam
Wed Apr 22 12:54:31 2020 [pid 17467] CONNECT: Client "113.78.64.97"
Wed Apr 22 12:54:31 2020 [pid 17466] [anonymous] FAIL LOGIN: Client "113.78.64.97"
Wed Apr 22 12:54:33 2020 [pid 17469] CONNECT: Client "113.78.64.97"
Wed Apr 22 12:54:33 2020 [pid 17468] [www] FAIL LOGIN: Client "113.78.64.97"
Wed Apr 22 12:54:35 2020 [pid 17471] CONNECT: Client "113.78.64.97"
...
2020-04-22 20:55:15
185.50.149.5 attackspam
Apr 22 13:59:40 srv01 postfix/smtpd\[26967\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 22 13:59:59 srv01 postfix/smtpd\[25172\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 22 14:07:59 srv01 postfix/smtpd\[6444\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 22 14:08:16 srv01 postfix/smtpd\[26967\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 22 14:10:18 srv01 postfix/smtpd\[4803\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-04-22 20:41:36
185.176.27.246 attack
04/22/2020-09:05:52.937361 185.176.27.246 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-04-22 21:08:49
111.67.193.92 attackbots
Apr 22 02:01:26 web1 sshd\[4996\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.193.92  user=root
Apr 22 02:01:28 web1 sshd\[4996\]: Failed password for root from 111.67.193.92 port 59500 ssh2
Apr 22 02:04:41 web1 sshd\[5369\]: Invalid user ug from 111.67.193.92
Apr 22 02:04:41 web1 sshd\[5369\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.193.92
Apr 22 02:04:43 web1 sshd\[5369\]: Failed password for invalid user ug from 111.67.193.92 port 55078 ssh2
2020-04-22 20:39:58
111.206.198.92 attackbots
Bad bot/spoofed identity
2020-04-22 21:00:10
37.59.100.22 attackspam
Apr 22 09:23:07 firewall sshd[2815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.100.22
Apr 22 09:23:07 firewall sshd[2815]: Invalid user sg from 37.59.100.22
Apr 22 09:23:10 firewall sshd[2815]: Failed password for invalid user sg from 37.59.100.22 port 42766 ssh2
...
2020-04-22 20:34:10
123.207.142.31 attackbotsspam
Apr 22 14:00:56 sip sshd[23100]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.142.31
Apr 22 14:00:58 sip sshd[23100]: Failed password for invalid user admin from 123.207.142.31 port 58762 ssh2
Apr 22 14:14:56 sip sshd[28353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.142.31
2020-04-22 20:52:07
142.4.7.212 attack
CMS (WordPress or Joomla) login attempt.
2020-04-22 20:44:57
106.52.93.51 attack
Apr 22 13:54:56 rotator sshd\[8255\]: Failed password for root from 106.52.93.51 port 54008 ssh2Apr 22 13:57:55 rotator sshd\[9041\]: Invalid user teste from 106.52.93.51Apr 22 13:57:57 rotator sshd\[9041\]: Failed password for invalid user teste from 106.52.93.51 port 59840 ssh2Apr 22 14:01:04 rotator sshd\[9867\]: Invalid user ml from 106.52.93.51Apr 22 14:01:06 rotator sshd\[9867\]: Failed password for invalid user ml from 106.52.93.51 port 37438 ssh2Apr 22 14:04:18 rotator sshd\[9919\]: Failed password for root from 106.52.93.51 port 43282 ssh2
...
2020-04-22 21:07:05
106.12.209.117 attack
Apr 22 15:20:41 hosting sshd[11224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.117  user=root
Apr 22 15:20:43 hosting sshd[11224]: Failed password for root from 106.12.209.117 port 47710 ssh2
Apr 22 15:28:59 hosting sshd[11886]: Invalid user test from 106.12.209.117 port 58680
...
2020-04-22 21:06:20
183.15.177.0 attack
Lines containing failures of 183.15.177.0
Apr 22 10:17:22 shared03 sshd[28066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.15.177.0  user=r.r
Apr 22 10:17:24 shared03 sshd[28066]: Failed password for r.r from 183.15.177.0 port 29681 ssh2
Apr 22 10:17:25 shared03 sshd[28066]: Received disconnect from 183.15.177.0 port 29681:11: Bye Bye [preauth]
Apr 22 10:17:25 shared03 sshd[28066]: Disconnected from authenticating user r.r 183.15.177.0 port 29681 [preauth]
Apr 22 10:53:52 shared03 sshd[10782]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.15.177.0  user=r.r
Apr 22 10:53:54 shared03 sshd[10782]: Failed password for r.r from 183.15.177.0 port 62918 ssh2
Apr 22 10:53:54 shared03 sshd[10782]: Received disconnect from 183.15.177.0 port 62918:11: Bye Bye [preauth]
Apr 22 10:53:54 shared03 sshd[10782]: Disconnected from authenticating user r.r 183.15.177.0 port 62918 [preauth]
Apr 22 ........
------------------------------
2020-04-22 20:38:15

最近上报的IP列表

86.81.176.7 63.252.206.39 7.99.251.117 180.186.235.142
188.250.75.78 221.99.238.111 171.212.196.194 255.180.176.57
77.209.177.218 69.252.74.174 210.121.63.167 184.174.147.236
101.37.240.161 114.53.30.20 215.111.106.74 44.199.99.23
249.199.176.109 215.242.12.90 250.29.12.200 252.229.177.234