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

;; QUESTION SECTION:
;148.159.118.217.		IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 17:30:27 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 217.118.159.148.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 148.159.118.217.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
74.207.242.199 attack
Port 22 Scan, PTR: None
2020-02-11 21:36:44
188.17.159.203 attackbotsspam
Feb  9 19:58:17 garuda sshd[911374]: reveeclipse mapping checking getaddrinfo for dsl-188-17-159-203.permonline.ru [188.17.159.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  9 19:58:17 garuda sshd[911374]: Invalid user adj from 188.17.159.203
Feb  9 19:58:17 garuda sshd[911374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.17.159.203 
Feb  9 19:58:19 garuda sshd[911374]: Failed password for invalid user adj from 188.17.159.203 port 55226 ssh2
Feb  9 19:58:19 garuda sshd[911374]: Received disconnect from 188.17.159.203: 11: Bye Bye [preauth]
Feb  9 20:23:11 garuda sshd[917696]: reveeclipse mapping checking getaddrinfo for dsl-188-17-159-203.permonline.ru [188.17.159.203] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  9 20:23:11 garuda sshd[917696]: Invalid user vnk from 188.17.159.203
Feb  9 20:23:11 garuda sshd[917696]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.17.159.203 
Feb  9 2........
-------------------------------
2020-02-11 22:18:01
103.90.99.18 attackspambots
unauthorized connection attempt
2020-02-11 21:34:58
188.36.146.149 attackbotsspam
Feb 11 14:42:43 srv-ubuntu-dev3 sshd[62554]: Invalid user dfw from 188.36.146.149
Feb 11 14:42:43 srv-ubuntu-dev3 sshd[62554]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.36.146.149
Feb 11 14:42:43 srv-ubuntu-dev3 sshd[62554]: Invalid user dfw from 188.36.146.149
Feb 11 14:42:46 srv-ubuntu-dev3 sshd[62554]: Failed password for invalid user dfw from 188.36.146.149 port 54486 ssh2
Feb 11 14:45:55 srv-ubuntu-dev3 sshd[62813]: Invalid user zgk from 188.36.146.149
Feb 11 14:45:55 srv-ubuntu-dev3 sshd[62813]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.36.146.149
Feb 11 14:45:55 srv-ubuntu-dev3 sshd[62813]: Invalid user zgk from 188.36.146.149
Feb 11 14:45:57 srv-ubuntu-dev3 sshd[62813]: Failed password for invalid user zgk from 188.36.146.149 port 54474 ssh2
Feb 11 14:49:07 srv-ubuntu-dev3 sshd[63026]: Invalid user buw from 188.36.146.149
...
2020-02-11 21:52:28
77.42.94.99 attackspambots
unauthorized connection attempt
2020-02-11 21:36:15
78.128.113.133 attackspambots
Feb 11 14:08:00 mail postfix/smtpd\[16960\]: warning: unknown\[78.128.113.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Feb 11 14:08:07 mail postfix/smtpd\[16960\]: warning: unknown\[78.128.113.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Feb 11 14:50:40 mail postfix/smtpd\[18273\]: warning: unknown\[78.128.113.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Feb 11 14:50:47 mail postfix/smtpd\[18273\]: warning: unknown\[78.128.113.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-02-11 21:57:35
222.186.30.209 attackbotsspam
Feb 11 14:48:41 MK-Soft-VM4 sshd[1059]: Failed password for root from 222.186.30.209 port 39473 ssh2
...
2020-02-11 21:50:52
80.66.81.36 attack
Feb 11 13:46:37 heicom postfix/smtpd\[9776\]: warning: unknown\[80.66.81.36\]: SASL LOGIN authentication failed: authentication failure
Feb 11 13:46:47 heicom postfix/smtpd\[9776\]: warning: unknown\[80.66.81.36\]: SASL LOGIN authentication failed: authentication failure
Feb 11 13:47:42 heicom postfix/smtpd\[9776\]: warning: unknown\[80.66.81.36\]: SASL LOGIN authentication failed: authentication failure
Feb 11 13:47:51 heicom postfix/smtpd\[9776\]: warning: unknown\[80.66.81.36\]: SASL LOGIN authentication failed: authentication failure
Feb 11 13:49:06 heicom postfix/smtpd\[9776\]: warning: unknown\[80.66.81.36\]: SASL LOGIN authentication failed: authentication failure
...
2020-02-11 21:54:59
182.113.207.20 attack
Telnet/23 MH Probe, BF, Hack -
2020-02-11 22:10:41
181.170.144.227 attackbots
Automatic report - Port Scan Attack
2020-02-11 22:22:08
181.126.89.244 attackbots
unauthorized connection attempt
2020-02-11 21:45:03
49.36.158.201 attackbots
1581428937 - 02/11/2020 14:48:57 Host: 49.36.158.201/49.36.158.201 Port: 445 TCP Blocked
2020-02-11 22:07:20
177.37.77.64 attackspambots
(sshd) Failed SSH login from 177.37.77.64 (BR/Brazil/177-37-77-64.ultrat.com.br): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 11 14:49:01 ubnt-55d23 sshd[4051]: Invalid user xuj from 177.37.77.64 port 45041
Feb 11 14:49:02 ubnt-55d23 sshd[4055]: Invalid user xuj from 177.37.77.64 port 45083
2020-02-11 21:53:38
222.186.52.78 attack
Feb 11 14:47:34 * sshd[11875]: Failed password for root from 222.186.52.78 port 15511 ssh2
2020-02-11 22:16:31
27.20.196.160 attackbotsspam
Telnet/23 MH Probe, BF, Hack -
2020-02-11 21:51:47

Recently Reported IPs

152.233.118.240 44.88.191.119 255.114.41.20 211.218.76.126
211.97.82.42 81.224.8.68 33.161.244.163 18.173.188.49
136.42.204.242 60.177.78.21 147.87.184.165 101.24.51.15
220.74.60.54 6.18.191.3 163.84.164.117 230.255.182.16
255.75.186.197 51.133.12.235 62.200.194.23 98.104.117.151