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

Region: Ohio

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

;; QUESTION SECTION:
;3.148.201.114.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 26 02:00:02 CST 2025
;; MSG SIZE  rcvd: 106
Host info
114.201.148.3.in-addr.arpa domain name pointer ec2-3-148-201-114.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
114.201.148.3.in-addr.arpa	name = ec2-3-148-201-114.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.226.118.45 attack
SSH/22 MH Probe, BF, Hack -
2020-01-01 00:22:52
218.107.213.89 attackbots
Dec 31 15:52:41 host postfix/smtpd[57641]: warning: unknown[218.107.213.89]: SASL LOGIN authentication failed: authentication failure
Dec 31 15:52:45 host postfix/smtpd[57641]: warning: unknown[218.107.213.89]: SASL LOGIN authentication failed: authentication failure
...
2020-01-01 00:06:43
52.178.218.186 attackbots
191231  9:40:18 [Warning] Access denied for user 'root'@'52.178.218.186' (using password: YES)
191231  9:40:18 [Warning] Access denied for user 'root'@'52.178.218.186' (using password: YES)
191231  9:40:18 [Warning] Access denied for user 'root'@'52.178.218.186' (using password: YES)
...
2020-01-01 00:23:28
77.237.77.207 attackbotsspam
Dec 31 17:01:09 localhost sshd\[29201\]: Invalid user asahi from 77.237.77.207 port 44930
Dec 31 17:01:09 localhost sshd\[29201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.237.77.207
Dec 31 17:01:11 localhost sshd\[29201\]: Failed password for invalid user asahi from 77.237.77.207 port 44930 ssh2
2020-01-01 00:33:52
50.53.179.3 attackbotsspam
1577803881 - 12/31/2019 15:51:21 Host: 50.53.179.3/50.53.179.3 Port: 22 TCP Blocked
2020-01-01 00:51:37
185.94.111.1 attack
185.94.111.1 was recorded 6 times by 5 hosts attempting to connect to the following ports: 389,11211. Incident counter (4h, 24h, all-time): 6, 52, 6666
2020-01-01 00:40:49
112.85.42.237 attack
Dec 31 16:29:21 localhost sshd\[130249\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237  user=root
Dec 31 16:29:23 localhost sshd\[130249\]: Failed password for root from 112.85.42.237 port 23959 ssh2
Dec 31 16:29:25 localhost sshd\[130249\]: Failed password for root from 112.85.42.237 port 23959 ssh2
Dec 31 16:29:27 localhost sshd\[130249\]: Failed password for root from 112.85.42.237 port 23959 ssh2
Dec 31 16:32:50 localhost sshd\[130344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237  user=root
...
2020-01-01 00:39:12
137.59.162.169 attackspambots
2019-12-31T15:57:58.905425shield sshd\[8163\]: Invalid user rodger from 137.59.162.169 port 34129
2019-12-31T15:57:58.911461shield sshd\[8163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.59.162.169
2019-12-31T15:58:00.401219shield sshd\[8163\]: Failed password for invalid user rodger from 137.59.162.169 port 34129 ssh2
2019-12-31T16:06:22.924802shield sshd\[9540\]: Invalid user oleg123 from 137.59.162.169 port 47567
2019-12-31T16:06:22.929048shield sshd\[9540\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.59.162.169
2020-01-01 00:06:28
45.136.108.13 attackbots
RDP Bruteforce
2020-01-01 00:21:19
5.77.27.19 attack
19/12/31@10:58:18: FAIL: Alarm-Network address from=5.77.27.19
...
2020-01-01 00:11:41
62.28.160.141 attackbotsspam
Port scan: Attack repeated for 24 hours
2020-01-01 00:48:02
185.176.27.34 attack
12/31/2019-09:52:23.630949 185.176.27.34 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-01-01 00:17:02
83.103.98.211 attackspambots
Dec 31 17:41:28 localhost sshd\[32496\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.103.98.211  user=root
Dec 31 17:41:30 localhost sshd\[32496\]: Failed password for root from 83.103.98.211 port 23274 ssh2
Dec 31 17:43:13 localhost sshd\[32630\]: Invalid user rouch from 83.103.98.211 port 63163
2020-01-01 00:49:36
218.92.0.212 attackbots
Triggered by Fail2Ban at Vostok web server
2020-01-01 00:28:55
5.196.201.5 attackbots
Dec 31 17:07:35 relay postfix/smtpd\[17686\]: warning: unknown\[5.196.201.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 17:11:12 relay postfix/smtpd\[17688\]: warning: unknown\[5.196.201.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 17:14:47 relay postfix/smtpd\[26063\]: warning: unknown\[5.196.201.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 17:18:23 relay postfix/smtpd\[26053\]: warning: unknown\[5.196.201.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 31 17:22:02 relay postfix/smtpd\[17688\]: warning: unknown\[5.196.201.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-01 00:35:12

Recently Reported IPs

64.31.4.105 165.154.112.17 103.153.78.242 94.74.164.59
92.118.39.86 87.120.191.84 185.174.137.218 91.230.168.207
91.230.168.205 195.184.76.156 123.174.81.187 222.79.103.59
20.84.166.43 206.168.34.117 125.47.54.246 136.132.136.136
43.242.202.244 113.95.134.106 101.133.224.44 98.81.240.68