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

;; QUESTION SECTION:
;149.98.248.1.			IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 20:10:48 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 1.248.98.149.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 1.248.98.149.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
18.233.131.167 attackbots
2020-01-27T06:21:30.637629shield sshd\[16274\]: Invalid user cyyang from 18.233.131.167 port 33202
2020-01-27T06:21:30.641844shield sshd\[16274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-233-131-167.compute-1.amazonaws.com
2020-01-27T06:21:32.277857shield sshd\[16274\]: Failed password for invalid user cyyang from 18.233.131.167 port 33202 ssh2
2020-01-27T06:23:41.604861shield sshd\[17116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-233-131-167.compute-1.amazonaws.com  user=games
2020-01-27T06:23:43.896385shield sshd\[17116\]: Failed password for games from 18.233.131.167 port 55578 ssh2
2020-01-27 14:55:52
91.88.83.76 attackspambots
Unauthorized connection attempt detected from IP address 91.88.83.76 to port 5555 [J]
2020-01-27 15:20:30
200.146.248.82 attackbotsspam
Unauthorized connection attempt detected from IP address 200.146.248.82 to port 81 [J]
2020-01-27 15:00:13
178.95.103.52 attack
Unauthorized connection attempt detected from IP address 178.95.103.52 to port 23 [J]
2020-01-27 15:09:28
212.77.138.155 attack
Unauthorized connection attempt detected from IP address 212.77.138.155 to port 80 [J]
2020-01-27 14:58:50
99.229.149.192 attack
20/1/27@01:51:38: FAIL: Alarm-Telnet address from=99.229.149.192
...
2020-01-27 15:18:45
73.57.174.148 attack
Unauthorized connection attempt detected from IP address 73.57.174.148 to port 81 [J]
2020-01-27 14:53:22
124.156.197.29 attack
Unauthorized connection attempt detected from IP address 124.156.197.29 to port 1467 [J]
2020-01-27 15:10:56
79.137.72.171 attackspam
Unauthorized connection attempt detected from IP address 79.137.72.171 to port 2220 [J]
2020-01-27 14:51:40
117.93.112.17 attackspambots
Unauthorized connection attempt detected from IP address 117.93.112.17 to port 2222 [J]
2020-01-27 15:13:40
37.204.144.53 attackbotsspam
Unauthorized connection attempt detected from IP address 37.204.144.53 to port 22 [J]
2020-01-27 14:54:58
122.51.107.227 attackspambots
Unauthorized connection attempt detected from IP address 122.51.107.227 to port 2220 [J]
2020-01-27 15:12:07
47.205.188.9 attack
Unauthorized connection attempt detected from IP address 47.205.188.9 to port 81 [J]
2020-01-27 14:54:23
59.21.153.84 attack
Unauthorized connection attempt detected from IP address 59.21.153.84 to port 23 [J]
2020-01-27 14:53:41
78.13.211.11 attackspam
Unauthorized connection attempt detected from IP address 78.13.211.11 to port 88 [J]
2020-01-27 15:21:30

Recently Reported IPs

239.156.134.181 69.223.66.228 5.181.218.208 242.208.164.175
80.248.31.24 107.199.93.73 30.185.145.244 134.216.189.65
76.128.128.248 23.3.177.58 218.224.249.36 188.167.111.123
150.136.141.27 211.28.70.79 69.162.0.149 93.23.140.171
117.154.14.25 192.236.25.107 94.175.160.59 37.30.133.254