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: Multicast Address

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

;; QUESTION SECTION:
;224.138.48.148.			IN	A

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

;; Query time: 44 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 16:08:29 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 148.48.138.224.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 148.48.138.224.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.158.213.148 spam
info@jackrabbit.co.nz which send to :
http://www.superpuperr.blogspot.com/p9okhbhjbrftfp9okgvkjn => Google => Yahoo => Yeah etc. => abusecomplaints@markmonitor.com
Message-ID: <0602d3e3e8c316e5c63442111acef24e6de0e44e91@jackrabbit.co.nz> => 210.131.0.50
jackrabbit.co.nz => 104.18.55.251
210.131.0.50 => hostmaster@nic.ad.jp
https://en.asytech.cn/report-ip/210.131.0.50
nifty.com => tech-contact@nifty.ad.jp, nifty-admin@list.nifty.co.jp, nifty-tec@list.nifty.co.jp, gtld-abuse@jprs.jp
https://www.mywot.com/scorecard/bizmail.nifty.com
https://www.mywot.com/scorecard/nifty.com
nifty.com => 222.158.213.148
2020-02-22 04:07:40
195.95.147.98 attack
Feb 21 16:08:44 debian-2gb-nbg1-2 kernel: \[4556931.926813\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=195.95.147.98 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=57799 PROTO=TCP SPT=58686 DPT=2580 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-22 04:32:07
45.118.151.85 attack
Feb 21 18:32:41 ift sshd\[28952\]: Invalid user lijin from 45.118.151.85Feb 21 18:32:43 ift sshd\[28952\]: Failed password for invalid user lijin from 45.118.151.85 port 53334 ssh2Feb 21 18:36:03 ift sshd\[29518\]: Invalid user yyg from 45.118.151.85Feb 21 18:36:06 ift sshd\[29518\]: Failed password for invalid user yyg from 45.118.151.85 port 53728 ssh2Feb 21 18:39:24 ift sshd\[29984\]: Invalid user kevin from 45.118.151.85
...
2020-02-22 04:07:31
178.173.158.58 attackspam
Unauthorized connection attempt from IP address 178.173.158.58 on Port 445(SMB)
2020-02-22 04:18:02
128.14.137.182 attackbots
Port 443 (HTTPS) access denied
2020-02-22 04:22:51
51.77.148.77 attackbots
Feb 21 17:32:56 haigwepa sshd[9367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.148.77 
Feb 21 17:32:57 haigwepa sshd[9367]: Failed password for invalid user penglina from 51.77.148.77 port 52326 ssh2
...
2020-02-22 04:30:22
185.90.22.114 attackbots
TCP src-port=15769   dst-port=25   Listed on   spam-sorbs rbldns-ru         (235)
2020-02-22 04:19:42
188.170.13.225 attack
Feb 21 14:22:08 vps sshd[29653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.170.13.225 
Feb 21 14:22:11 vps sshd[29653]: Failed password for invalid user dev from 188.170.13.225 port 38948 ssh2
Feb 21 14:30:44 vps sshd[30097]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.170.13.225 
...
2020-02-22 04:19:13
219.85.0.65 attackbots
1582290686 - 02/21/2020 14:11:26 Host: 219.85.0.65/219.85.0.65 Port: 445 TCP Blocked
2020-02-22 04:25:38
121.192.181.171 attackspam
Feb 21 04:42:28 hanapaa sshd\[5470\]: Invalid user yamaguchi from 121.192.181.171
Feb 21 04:42:28 hanapaa sshd\[5470\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.192.181.171
Feb 21 04:42:30 hanapaa sshd\[5470\]: Failed password for invalid user yamaguchi from 121.192.181.171 port 47092 ssh2
Feb 21 04:45:49 hanapaa sshd\[5729\]: Invalid user gongmq from 121.192.181.171
Feb 21 04:45:49 hanapaa sshd\[5729\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.192.181.171
2020-02-22 04:26:25
222.186.138.49 attackbots
suspicious action Fri, 21 Feb 2020 10:11:06 -0300
2020-02-22 04:37:18
122.115.38.196 attackbotsspam
suspicious action Fri, 21 Feb 2020 10:11:37 -0300
2020-02-22 04:20:58
77.247.108.88 attack
suspicious action Fri, 21 Feb 2020 10:10:54 -0300
2020-02-22 04:41:40
188.254.0.160 attackbots
DATE:2020-02-21 18:43:01, IP:188.254.0.160, PORT:ssh SSH brute force auth (docker-dc)
2020-02-22 04:09:01
106.51.230.186 attackspam
Feb 21 13:47:08 Tower sshd[9552]: Connection from 106.51.230.186 port 54426 on 192.168.10.220 port 22 rdomain ""
Feb 21 13:47:09 Tower sshd[9552]: Invalid user alesiashavel from 106.51.230.186 port 54426
Feb 21 13:47:09 Tower sshd[9552]: error: Could not get shadow information for NOUSER
Feb 21 13:47:09 Tower sshd[9552]: Failed password for invalid user alesiashavel from 106.51.230.186 port 54426 ssh2
Feb 21 13:47:09 Tower sshd[9552]: Received disconnect from 106.51.230.186 port 54426:11: Bye Bye [preauth]
Feb 21 13:47:09 Tower sshd[9552]: Disconnected from invalid user alesiashavel 106.51.230.186 port 54426 [preauth]
2020-02-22 04:09:29

Recently Reported IPs

55.156.220.208 73.103.183.94 121.214.143.14 38.6.169.223
253.178.41.16 227.202.184.105 73.4.91.161 118.185.81.172
213.34.96.123 52.1.195.167 2.231.165.29 133.0.224.98
22.213.109.159 25.69.249.183 14.221.16.105 231.206.18.164
108.197.137.174 191.137.47.196 42.207.71.16 75.22.186.78