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

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;116.239.102.149.		IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 00:25:44 CST 2025
;; MSG SIZE  rcvd: 108
HOST信息:
Host 149.102.239.116.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 149.102.239.116.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
77.42.88.155 attack
Unauthorized connection attempt detected from IP address 77.42.88.155 to port 23
2020-01-11 07:09:05
198.211.123.183 attackbots
Jan 10 18:48:29 : SSH login attempts with invalid user
2020-01-11 07:23:57
187.16.96.37 attackspam
Jan 11 02:10:05 gw1 sshd[30844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.16.96.37
Jan 11 02:10:07 gw1 sshd[30844]: Failed password for invalid user knut from 187.16.96.37 port 55056 ssh2
...
2020-01-11 07:00:54
107.175.32.78 attackbots
(From eric@talkwithcustomer.com) Hello wardchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website wardchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website wardchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one f
2020-01-11 06:52:36
180.179.196.84 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-11 07:29:14
37.49.231.168 attackspam
Jan 10 22:09:40 debian-2gb-nbg1-2 kernel: \[949890.218838\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=37.49.231.168 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=56277 PROTO=TCP SPT=48486 DPT=8081 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-11 07:26:42
111.225.204.32 attack
Fail2Ban - FTP Abuse Attempt
2020-01-11 07:22:36
47.9.118.157 attackspam
Chat Spam
2020-01-11 07:27:57
88.248.183.7 attackspambots
Honeypot attack, port: 445, PTR: 88.248.183.7.static.ttnet.com.tr.
2020-01-11 07:20:14
190.143.39.211 attackspambots
Jan 10 22:10:08 odroid64 sshd\[16648\]: User root from 190.143.39.211 not allowed because not listed in AllowUsers
Jan 10 22:10:08 odroid64 sshd\[16648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.143.39.211  user=root
...
2020-01-11 06:59:44
82.253.104.164 attack
SASL PLAIN auth failed: ruser=...
2020-01-11 07:17:59
132.232.7.197 attackbots
Jan 10 23:48:08 localhost sshd\[22495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197  user=root
Jan 10 23:48:10 localhost sshd\[22495\]: Failed password for root from 132.232.7.197 port 50736 ssh2
Jan 10 23:50:40 localhost sshd\[22666\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197  user=root
Jan 10 23:50:42 localhost sshd\[22666\]: Failed password for root from 132.232.7.197 port 43984 ssh2
Jan 10 23:53:07 localhost sshd\[22692\]: Invalid user testing from 132.232.7.197
...
2020-01-11 06:53:10
117.247.190.142 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-01-11 07:13:04
90.73.243.149 attack
Lines containing failures of 90.73.243.149
Jan  7 14:45:00 icinga sshd[30047]: Invalid user mb from 90.73.243.149 port 41602
Jan  7 14:45:00 icinga sshd[30047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.73.243.149
Jan  7 14:45:01 icinga sshd[30047]: Failed password for invalid user mb from 90.73.243.149 port 41602 ssh2
Jan  7 14:45:01 icinga sshd[30047]: Received disconnect from 90.73.243.149 port 41602:11: Bye Bye [preauth]
Jan  7 14:45:01 icinga sshd[30047]: Disconnected from invalid user mb 90.73.243.149 port 41602 [preauth]
Jan  7 15:39:57 icinga sshd[12414]: Invalid user jira from 90.73.243.149 port 36032
Jan  7 15:39:57 icinga sshd[12414]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.73.243.149


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=90.73.243.149
2020-01-11 07:05:23
78.47.155.67 attack
78.47.155.67 - - - [10/Jan/2020:21:09:55 +0000] "GET //wp-content/plugins/apikey/apikey.php?test=hello HTTP/1.1" 404 162 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0" "-" "XMLHttpRequest"
2020-01-11 07:14:00

最近上报的IP列表

81.156.237.81 143.5.213.146 19.56.58.95 205.7.149.39
228.163.71.213 247.33.41.207 250.155.195.48 49.158.157.116
72.193.166.186 163.143.138.151 76.176.169.182 205.179.184.95
211.159.191.18 181.45.204.81 100.40.107.160 72.86.203.253
168.127.196.89 104.228.42.206 124.199.29.211 106.81.232.89