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

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

;; QUESTION SECTION:
;148.12.119.137.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 31 23:31:37 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 137.119.12.148.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 137.119.12.148.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
64.225.5.137 attackspambots
Aug 28 12:16:27 lukav-desktop sshd\[8052\]: Invalid user ttt from 64.225.5.137
Aug 28 12:16:27 lukav-desktop sshd\[8052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.5.137
Aug 28 12:16:29 lukav-desktop sshd\[8052\]: Failed password for invalid user ttt from 64.225.5.137 port 33874 ssh2
Aug 28 12:24:11 lukav-desktop sshd\[8274\]: Invalid user jms from 64.225.5.137
Aug 28 12:24:11 lukav-desktop sshd\[8274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.5.137
2020-08-28 18:10:58
91.193.5.58 attack
Port scanning [3 denied]
2020-08-28 18:00:08
192.241.221.215 attack
Port scan denied
2020-08-28 18:33:27
221.122.119.50 attackbotsspam
Invalid user el from 221.122.119.50 port 59797
2020-08-28 18:36:30
67.213.73.123 attackspam
2212/tcp 221/tcp 52000/tcp...
[2020-08-18/28]17pkt,9pt.(tcp)
2020-08-28 18:28:00
89.248.162.161 attack
1146/tcp 1234/tcp 1310/tcp...⊂ [1000/tcp,2376/tcp]∪152port
[2020-07-18/08-28]1667pkt,1529pt.(tcp)
2020-08-28 18:22:22
185.55.164.32 botsproxy
185.55.164.0/22
2020-08-28 18:16:23
190.85.28.154 attackbotsspam
Invalid user tt from 190.85.28.154 port 42838
2020-08-28 18:13:07
139.198.122.19 attackspam
Aug 28 13:09:58 ift sshd\[34280\]: Invalid user flw from 139.198.122.19Aug 28 13:10:00 ift sshd\[34280\]: Failed password for invalid user flw from 139.198.122.19 port 60652 ssh2Aug 28 13:13:07 ift sshd\[34958\]: Invalid user elsa from 139.198.122.19Aug 28 13:13:08 ift sshd\[34958\]: Failed password for invalid user elsa from 139.198.122.19 port 45006 ssh2Aug 28 13:16:12 ift sshd\[35451\]: Invalid user zxc from 139.198.122.19
...
2020-08-28 18:29:34
175.155.96.197 attackspam
Unauthorized connection attempt detected from IP address 175.155.96.197 to port 23 [T]
2020-08-28 18:21:24
1.1.227.82 attackbots
20/8/27@23:48:24: FAIL: Alarm-Network address from=1.1.227.82
...
2020-08-28 18:27:24
47.91.44.93 attackspam
TCP port : 24937
2020-08-28 18:16:24
2a02:6b8:c0c:4902:0:492c:2af8:0 attack
Detected By Fail2ban
2020-08-28 18:09:28
185.143.223.245 attackspam
Port scan denied
2020-08-28 18:11:14
1.27.91.196 attackbots
Port probing on unauthorized port 23
2020-08-28 18:28:51

Recently Reported IPs

186.173.96.24 249.150.253.217 43.119.126.177 63.83.227.33
178.140.216.27 135.109.6.92 222.34.7.78 58.116.102.244
157.150.139.47 177.231.105.206 35.250.47.47 247.207.48.141
229.73.152.250 155.38.146.169 95.51.242.6 197.186.231.225
61.119.30.4 150.79.78.110 121.105.175.42 12.24.142.41