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

;; QUESTION SECTION:
;158.118.42.154.			IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 18:32:11 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 154.42.118.158.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 158.118.42.154.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
195.154.169.186 attackspambots
Oct 21 07:05:09 sauna sshd[103579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.154.169.186
Oct 21 07:05:12 sauna sshd[103579]: Failed password for invalid user nvidia from 195.154.169.186 port 41950 ssh2
...
2019-10-21 17:28:24
201.55.33.90 attack
ssh brute force
2019-10-21 17:23:39
91.121.101.159 attackspambots
Invalid user oracle from 91.121.101.159 port 49842
2019-10-21 17:21:35
220.88.1.208 attack
Tried sshing with brute force.
2019-10-21 17:56:54
79.143.22.50 attackspambots
BURG,WP GET /wp-login.php
2019-10-21 17:38:35
140.249.22.238 attackspambots
Oct 20 23:33:34 hpm sshd\[22096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.249.22.238  user=root
Oct 20 23:33:37 hpm sshd\[22096\]: Failed password for root from 140.249.22.238 port 46210 ssh2
Oct 20 23:38:30 hpm sshd\[22487\]: Invalid user user from 140.249.22.238
Oct 20 23:38:30 hpm sshd\[22487\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.249.22.238
Oct 20 23:38:33 hpm sshd\[22487\]: Failed password for invalid user user from 140.249.22.238 port 55406 ssh2
2019-10-21 17:49:20
138.36.96.46 attack
Oct 20 23:29:59 hpm sshd\[21744\]: Invalid user 123456 from 138.36.96.46
Oct 20 23:29:59 hpm sshd\[21744\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.36.96.46
Oct 20 23:30:02 hpm sshd\[21744\]: Failed password for invalid user 123456 from 138.36.96.46 port 44886 ssh2
Oct 20 23:35:04 hpm sshd\[22213\]: Invalid user apache123\$ from 138.36.96.46
Oct 20 23:35:04 hpm sshd\[22213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.36.96.46
2019-10-21 17:45:14
123.188.202.127 attack
Unauthorised access (Oct 21) SRC=123.188.202.127 LEN=40 TTL=114 ID=56931 TCP DPT=8080 WINDOW=43658 SYN 
Unauthorised access (Oct 20) SRC=123.188.202.127 LEN=40 TTL=114 ID=61557 TCP DPT=8080 WINDOW=29758 SYN 
Unauthorised access (Oct 20) SRC=123.188.202.127 LEN=40 TTL=114 ID=36291 TCP DPT=8080 WINDOW=47630 SYN
2019-10-21 17:39:51
123.168.88.80 attackbotsspam
Oct 21 03:45:59 sshgateway sshd\[21843\]: Invalid user plaza from 123.168.88.80
Oct 21 03:45:59 sshgateway sshd\[21843\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.168.88.80
Oct 21 03:46:01 sshgateway sshd\[21843\]: Failed password for invalid user plaza from 123.168.88.80 port 60382 ssh2
2019-10-21 17:42:19
169.255.10.134 attack
Oct 21 09:40:03 our-server-hostname postfix/smtpd[799]: connect from unknown[169.255.10.134]
Oct x@x
Oct 21 09:41:01 our-server-hostname postfix/smtpd[799]: lost connection after RCPT from unknown[169.255.10.134]
Oct 21 09:41:01 our-server-hostname postfix/smtpd[799]: disconnect from unknown[169.255.10.134]
Oct 21 11:48:42 our-server-hostname postfix/smtpd[29517]: connect from unknown[169.255.10.134]
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=169.255.10.134
2019-10-21 17:20:24
185.211.245.170 attackbots
SASL broute force
2019-10-21 17:32:26
188.213.64.107 attackspam
10/20/2019-23:46:08.111284 188.213.64.107 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-21 17:38:59
91.121.110.97 attackbotsspam
Oct 21 10:08:07 rotator sshd\[21369\]: Invalid user ts3 from 91.121.110.97Oct 21 10:08:08 rotator sshd\[21369\]: Failed password for invalid user ts3 from 91.121.110.97 port 58938 ssh2Oct 21 10:12:06 rotator sshd\[22251\]: Invalid user service from 91.121.110.97Oct 21 10:12:08 rotator sshd\[22251\]: Failed password for invalid user service from 91.121.110.97 port 41714 ssh2Oct 21 10:16:05 rotator sshd\[23091\]: Invalid user hack from 91.121.110.97Oct 21 10:16:06 rotator sshd\[23091\]: Failed password for invalid user hack from 91.121.110.97 port 52722 ssh2
...
2019-10-21 17:19:35
218.86.124.102 attackbotsspam
Multiple failed RDP login attempts
2019-10-21 17:28:02
222.186.175.215 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.215  user=root
Failed password for root from 222.186.175.215 port 34108 ssh2
Failed password for root from 222.186.175.215 port 34108 ssh2
Failed password for root from 222.186.175.215 port 34108 ssh2
Failed password for root from 222.186.175.215 port 34108 ssh2
2019-10-21 17:37:50

Recently Reported IPs

166.168.34.48 174.197.247.14 214.174.12.106 254.221.244.23
189.101.79.73 200.234.150.52 251.156.146.3 151.143.121.139
203.245.158.71 190.232.221.199 138.75.140.151 15.141.250.77
228.129.114.236 146.168.215.219 38.108.26.36 5.39.66.115
84.127.213.197 131.151.179.95 148.248.75.27 251.72.155.232