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: unknown

Region: unknown

Country: United States of America (the)

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 <<>> 134.121.220.248
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64171
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.121.220.248.		IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 00:47:35 CST 2025
;; MSG SIZE  rcvd: 108
Host info
b'Host 248.220.121.134.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
server can't find 134.121.220.248.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
119.158.108.84 attack
Hit on /wp-login.php
2019-06-24 10:09:33
211.250.187.247 attackbotsspam
Telnet Server BruteForce Attack
2019-06-24 10:45:16
45.14.151.10 attackbotsspam
Honeypot hit.
2019-06-24 10:33:54
173.89.120.26 attackspam
19/6/23@15:53:26: FAIL: IoT-SSH address from=173.89.120.26
...
2019-06-24 10:23:18
118.24.173.104 attack
Jun 24 03:30:34 v22019058497090703 sshd[4976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.173.104
Jun 24 03:30:37 v22019058497090703 sshd[4976]: Failed password for invalid user admin from 118.24.173.104 port 58401 ssh2
Jun 24 03:34:55 v22019058497090703 sshd[5211]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.173.104
...
2019-06-24 10:13:26
182.235.252.50 attack
" "
2019-06-24 10:39:22
159.65.128.166 attackbots
Automatic report - Web App Attack
2019-06-24 10:13:10
68.183.80.224 attackbotsspam
Jun 24 04:02:45 server2 sshd\[3577\]: User root from 68.183.80.224 not allowed because not listed in AllowUsers
Jun 24 04:02:46 server2 sshd\[3579\]: Invalid user admin from 68.183.80.224
Jun 24 04:02:48 server2 sshd\[3581\]: Invalid user admin from 68.183.80.224
Jun 24 04:02:49 server2 sshd\[3583\]: Invalid user user from 68.183.80.224
Jun 24 04:02:50 server2 sshd\[3585\]: Invalid user ubnt from 68.183.80.224
Jun 24 04:02:52 server2 sshd\[3587\]: Invalid user admin from 68.183.80.224
2019-06-24 10:44:40
114.97.133.116 attackbots
2019-06-23T22:12:32.137148mail01 postfix/smtpd[24604]: warning: unknown[114.97.133.116]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-23T22:12:40.371479mail01 postfix/smtpd[26594]: warning: unknown[114.97.133.116]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-23T22:12:51.289407mail01 postfix/smtpd[24604]: warning: unknown[114.97.133.116]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-24 10:47:21
187.61.122.162 attack
failed_logins
2019-06-24 10:14:39
14.18.248.22 attackbotsspam
SMB Server BruteForce Attack
2019-06-24 10:41:08
212.237.50.189 attackspam
5901/tcp 5901/tcp 5901/tcp...
[2019-04-23/06-22]6pkt,1pt.(tcp)
2019-06-24 10:54:24
54.39.15.178 attackspambots
ADMIN
2019-06-24 10:52:44
18.236.45.196 attack
Automatic report - Web App Attack
2019-06-24 10:44:19
178.128.81.125 attack
Jun 24 03:47:27 [munged] sshd[26632]: Invalid user glutton from 178.128.81.125 port 62940
Jun 24 03:47:27 [munged] sshd[26632]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.81.125
2019-06-24 10:14:00

Recently Reported IPs

182.152.144.17 196.97.104.153 17.15.78.149 52.204.223.3
154.142.214.14 140.226.192.145 73.87.171.167 93.90.205.119
123.156.122.158 83.212.84.142 249.252.133.212 113.62.247.243
127.67.162.98 163.12.217.13 124.194.125.195 66.102.35.169
61.196.42.125 224.19.148.61 77.36.238.149 103.62.248.246