Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Dorchester

Region: Massachusetts

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 158.121.214.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28286
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;158.121.214.214.		IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 14:35:09 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 214.214.121.158.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 214.214.121.158.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
172.105.151.142 attackbotsspam
172.105.151.142 was recorded 6 times by 6 hosts attempting to connect to the following ports: 19. Incident counter (4h, 24h, all-time): 6, 20, 20
2019-12-12 23:39:08
63.83.78.216 attackbotsspam
Autoban   63.83.78.216 AUTH/CONNECT
2019-12-12 23:40:39
63.83.78.236 attackspambots
Autoban   63.83.78.236 AUTH/CONNECT
2019-12-12 23:22:29
63.83.78.239 attack
Autoban   63.83.78.239 AUTH/CONNECT
2019-12-12 23:17:53
95.31.68.43 attackspam
23/tcp 5500/tcp 60001/tcp...
[2019-12-03/12]4pkt,3pt.(tcp)
2019-12-12 23:39:32
63.83.78.232 attackspambots
Autoban   63.83.78.232 AUTH/CONNECT
2019-12-12 23:29:20
63.83.78.244 attackbots
Autoban   63.83.78.244 AUTH/CONNECT
2019-12-12 23:14:13
63.83.78.242 attackspam
Autoban   63.83.78.242 AUTH/CONNECT
2019-12-12 23:15:50
200.44.50.155 attack
2019-12-12T14:54:11.423310shield sshd\[2040\]: Invalid user life from 200.44.50.155 port 42782
2019-12-12T14:54:11.428880shield sshd\[2040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.44.50.155
2019-12-12T14:54:13.782621shield sshd\[2040\]: Failed password for invalid user life from 200.44.50.155 port 42782 ssh2
2019-12-12T15:02:02.938151shield sshd\[4242\]: Invalid user root777 from 200.44.50.155 port 49850
2019-12-12T15:02:02.947321shield sshd\[4242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.44.50.155
2019-12-12 23:16:42
61.220.24.85 attackspam
1433/tcp 445/tcp...
[2019-11-12/12-12]4pkt,2pt.(tcp)
2019-12-12 23:08:26
220.191.220.247 attackspam
28080/tcp 8090/tcp 1433/tcp...
[2019-11-05/12-12]9pkt,4pt.(tcp)
2019-12-12 23:14:37
63.83.78.238 attack
Autoban   63.83.78.238 AUTH/CONNECT
2019-12-12 23:19:36
63.83.78.250 attack
Autoban   63.83.78.250 AUTH/CONNECT
2019-12-12 23:10:40
177.139.167.7 attackspam
Dec 12 15:44:08 work-partkepr sshd\[31229\]: User backup from 177.139.167.7 not allowed because not listed in AllowUsers
Dec 12 15:44:08 work-partkepr sshd\[31229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.139.167.7  user=backup
...
2019-12-12 23:46:53
63.83.78.208 attackbots
Autoban   63.83.78.208 AUTH/CONNECT
2019-12-12 23:48:40

Recently Reported IPs

99.33.161.191 237.0.7.53 93.44.115.238 66.15.210.123
233.174.112.156 23.172.183.131 39.155.59.189 204.125.163.84
168.227.29.104 198.185.152.120 79.32.63.141 146.156.22.214
79.182.220.12 79.236.203.21 28.35.241.169 209.10.161.15
25.196.8.12 106.45.175.239 230.122.22.31 92.247.85.5