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: North Charleston

Region: South Carolina

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:
IP Type Details Datetime
162.216.149.24 attack
Malicious IP
2024-05-09 23:13:24
162.216.149.158 attack
Malicious IP
2024-04-20 13:03:27
162.216.149.192 attack
Malicious IP / Malware
2024-04-13 01:54:06
162.216.149.74 proxy
VPN fraud
2023-06-08 13:32:58
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 162.216.149.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35506
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;162.216.149.242.		IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 04 16:30:50 CST 2025
;; MSG SIZE  rcvd: 108
Host info
242.149.216.162.in-addr.arpa domain name pointer 242.149.216.162.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.149.216.162.in-addr.arpa	name = 242.149.216.162.bc.googleusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
183.166.99.234 attack
SpamReport
2019-08-18 07:24:20
103.54.250.103 attackspambots
Invalid user roy from 103.54.250.103 port 59768
2019-08-18 07:45:17
195.206.105.217 attackspam
Aug 17 19:32:30 TORMINT sshd\[15195\]: Invalid user service from 195.206.105.217
Aug 17 19:32:30 TORMINT sshd\[15195\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.206.105.217
Aug 17 19:32:31 TORMINT sshd\[15195\]: Failed password for invalid user service from 195.206.105.217 port 41266 ssh2
...
2019-08-18 07:35:12
185.176.27.30 attackspambots
firewall-block, port(s): 26789/tcp
2019-08-18 07:50:43
148.70.202.114 attackspambots
2019-08-18T01:06:05.171977  sshd[32646]: Invalid user dspace from 148.70.202.114 port 56696
2019-08-18T01:06:05.181883  sshd[32646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.202.114
2019-08-18T01:06:05.171977  sshd[32646]: Invalid user dspace from 148.70.202.114 port 56696
2019-08-18T01:06:07.782676  sshd[32646]: Failed password for invalid user dspace from 148.70.202.114 port 56696 ssh2
2019-08-18T01:12:22.883553  sshd[32706]: Invalid user appuser from 148.70.202.114 port 41590
...
2019-08-18 08:02:06
121.186.14.44 attackspam
2019-08-17T22:56:39.509925abusebot.cloudsearch.cf sshd\[20908\]: Invalid user alumni from 121.186.14.44 port 65139
2019-08-18 07:29:02
27.208.220.219 attack
Invalid user service from 27.208.220.219 port 61114
2019-08-18 07:26:19
5.39.82.197 attackspambots
Invalid user juanda from 5.39.82.197 port 37276
2019-08-18 07:33:39
190.85.145.162 attack
Aug 17 23:09:58 DAAP sshd[8259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.145.162  user=root
Aug 17 23:10:01 DAAP sshd[8259]: Failed password for root from 190.85.145.162 port 51512 ssh2
Aug 17 23:14:34 DAAP sshd[8321]: Invalid user opuser from 190.85.145.162 port 42642
Aug 17 23:14:34 DAAP sshd[8321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.145.162
Aug 17 23:14:34 DAAP sshd[8321]: Invalid user opuser from 190.85.145.162 port 42642
Aug 17 23:14:37 DAAP sshd[8321]: Failed password for invalid user opuser from 190.85.145.162 port 42642 ssh2
...
2019-08-18 07:32:38
93.91.172.78 attackbots
Unauthorized connection attempt from IP address 93.91.172.78 on Port 445(SMB)
2019-08-18 07:23:41
154.8.228.143 attack
Aug 17 18:29:19 sshgateway sshd\[29915\]: Invalid user pinturabh from 154.8.228.143
Aug 17 18:29:19 sshgateway sshd\[29915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.8.228.143
Aug 17 18:29:21 sshgateway sshd\[29915\]: Failed password for invalid user pinturabh from 154.8.228.143 port 46233 ssh2
2019-08-18 08:03:54
213.225.214.202 attackbotsspam
Aug 17 20:29:55 bouncer sshd\[13291\]: Invalid user taku from 213.225.214.202 port 58331
Aug 17 20:29:55 bouncer sshd\[13291\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.225.214.202 
Aug 17 20:29:58 bouncer sshd\[13291\]: Failed password for invalid user taku from 213.225.214.202 port 58331 ssh2
...
2019-08-18 07:32:14
97.87.244.154 attackspam
2019-08-17T23:26:35.403084abusebot-6.cloudsearch.cf sshd\[17431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=97-87-244-154.static.sgnw.mi.charter.com  user=sshd
2019-08-18 07:44:13
49.231.15.15 attack
Scanning random ports - tries to find possible vulnerable services
2019-08-18 07:51:14
37.70.34.43 attackbotsspam
DATE:2019-08-17 20:29:54, IP:37.70.34.43, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-08-18 07:36:25

Recently Reported IPs

182.42.107.102 41.117.11.123 188.3.49.105 51.38.140.80
183.141.175.110 14.103.239.197 187.63.89.176 192.168.3.11
46.3.159.189 59.82.21.96 151.90.101.138 172.16.1.120
115.204.243.131 40.1.63.31 240.159.224.227 138.18.180.175
139.172.17.21 215.212.117.224 96.240.203.173 60.248.85.240