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

城市(city): unknown

省份(region): unknown

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): Comcast Cable Communications, LLC

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 74.145.21.138
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32158
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 0 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Tue Jun 11 00:43:27 CST 2019
;; MSG SIZE  rcvd: 117

HOST信息:
Host 138.21.145.74.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 138.21.145.74.in-addr.arpa: NXDOMAIN

相关IP信息:
最新评论:
IP 类型 评论内容 时间
122.51.96.57 attack
2020-09-29T20:18:24.831717paragon sshd[512663]: Invalid user internet from 122.51.96.57 port 34026
2020-09-29T20:18:24.835781paragon sshd[512663]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.96.57
2020-09-29T20:18:24.831717paragon sshd[512663]: Invalid user internet from 122.51.96.57 port 34026
2020-09-29T20:18:27.385199paragon sshd[512663]: Failed password for invalid user internet from 122.51.96.57 port 34026 ssh2
2020-09-29T20:21:24.534552paragon sshd[512758]: Invalid user samba from 122.51.96.57 port 38070
...
2020-09-30 00:29:07
23.108.4.58 attackbots
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with kckchiropractic.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any
2020-09-30 00:26:04
217.182.141.253 attack
Sep 29 18:33:46 cho sshd[3896952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.141.253 
Sep 29 18:33:46 cho sshd[3896952]: Invalid user cesar from 217.182.141.253 port 54457
Sep 29 18:33:48 cho sshd[3896952]: Failed password for invalid user cesar from 217.182.141.253 port 54457 ssh2
Sep 29 18:37:46 cho sshd[3897073]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.141.253  user=root
Sep 29 18:37:48 cho sshd[3897073]: Failed password for root from 217.182.141.253 port 59395 ssh2
...
2020-09-30 00:38:35
119.45.63.87 attack
Invalid user jacky from 119.45.63.87 port 48036
2020-09-30 00:29:40
122.51.187.118 attack
$f2bV_matches
2020-09-30 00:17:49
107.180.111.12 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2020-09-30 00:07:18
35.189.189.167 attackbots
Invalid user z from 35.189.189.167 port 54386
2020-09-30 00:02:00
68.183.66.73 attackspam
Port Scan/VNC login attempt
...
2020-09-30 00:19:51
87.251.70.79 attackbotsspam
port scan
2020-09-30 00:37:59
120.132.124.179 attackbots
 TCP (SYN) 120.132.124.179:14367 -> port 1433, len 40
2020-09-30 00:03:21
165.232.45.4 attack
21 attempts against mh-ssh on air
2020-09-29 23:58:33
187.200.137.146 attack
Lines containing failures of 187.200.137.146
Sep 28 14:31:05 newdogma sshd[3845]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.200.137.146  user=r.r
Sep 28 14:31:07 newdogma sshd[3845]: Failed password for r.r from 187.200.137.146 port 40836 ssh2
Sep 28 14:31:09 newdogma sshd[3845]: Received disconnect from 187.200.137.146 port 40836:11: Bye Bye [preauth]
Sep 28 14:31:09 newdogma sshd[3845]: Disconnected from authenticating user r.r 187.200.137.146 port 40836 [preauth]
Sep 28 14:42:58 newdogma sshd[4190]: Invalid user postgres3 from 187.200.137.146 port 50177
Sep 28 14:42:58 newdogma sshd[4190]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.200.137.146 
Sep 28 14:42:59 newdogma sshd[4190]: Failed password for invalid user postgres3 from 187.200.137.146 port 50177 ssh2
Sep 28 14:43:02 newdogma sshd[4190]: Received disconnect from 187.200.137.146 port 50177:11: Bye Bye [preauth]
Se........
------------------------------
2020-09-30 00:08:07
109.102.111.61 attackspambots
Automatic report - Banned IP Access
2020-09-30 00:06:59
206.189.132.8 attackbotsspam
Invalid user oracle2 from 206.189.132.8 port 33202
2020-09-30 00:22:08
45.141.84.126 attackbots
$f2bV_matches
2020-09-30 00:09:51

最近上报的IP列表

122.6.45.171 83.102.201.94 57.252.39.138 200.37.56.66
70.230.7.187 117.186.11.218 111.142.208.238 36.70.192.218
159.89.224.188 126.198.4.198 109.63.212.69 216.104.200.210
58.231.242.102 109.94.117.140 35.178.119.61 210.186.24.180
187.6.249.140 192.125.182.51 98.4.213.95 156.25.75.165