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: Lake Oswego

Region: Oregon

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

;; QUESTION SECTION:
;4.2.9.254.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 18:32:17 CST 2025
;; MSG SIZE  rcvd: 102
Host info
254.9.2.4.in-addr.arpa domain name pointer american-in.bar1.portland1.level3.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
254.9.2.4.in-addr.arpa	name = american-in.bar1.portland1.level3.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.29.78.244 attack
Chat Spam
2019-10-25 15:54:56
60.171.99.61 attack
23/tcp
[2019-10-25]1pkt
2019-10-25 15:56:10
188.254.0.182 attackbots
Oct 24 18:22:04 hanapaa sshd\[25071\]: Invalid user manas from 188.254.0.182
Oct 24 18:22:04 hanapaa sshd\[25071\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.182
Oct 24 18:22:07 hanapaa sshd\[25071\]: Failed password for invalid user manas from 188.254.0.182 port 39082 ssh2
Oct 24 18:26:19 hanapaa sshd\[25401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.182  user=root
Oct 24 18:26:21 hanapaa sshd\[25401\]: Failed password for root from 188.254.0.182 port 48378 ssh2
2019-10-25 15:39:17
207.46.13.209 attackbotsspam
Calling not existent HTTP content (400 or 404).
2019-10-25 15:53:09
170.78.40.20 attack
Oct 25 09:02:01 server2 sshd\[2347\]: Invalid user mongodb_user from 170.78.40.20
Oct 25 09:02:06 server2 sshd\[2363\]: Invalid user dashboard from 170.78.40.20
Oct 25 09:02:14 server2 sshd\[2374\]: Invalid user keycloak from 170.78.40.20
Oct 25 09:02:20 server2 sshd\[2376\]: Invalid user webserver from 170.78.40.20
Oct 25 09:02:26 server2 sshd\[2378\]: Invalid user abasmanage from 170.78.40.20
Oct 25 09:02:32 server2 sshd\[2382\]: Invalid user bsabmasterfile from 170.78.40.20
2019-10-25 15:25:53
81.29.215.84 attackbotsspam
fail2ban honeypot
2019-10-25 15:21:51
201.145.178.126 attackspambots
81/tcp
[2019-10-25]1pkt
2019-10-25 15:30:47
171.244.9.26 attack
SMB Server BruteForce Attack
2019-10-25 15:56:38
110.136.133.89 attack
445/tcp
[2019-10-25]1pkt
2019-10-25 15:24:25
199.249.230.79 attack
fail2ban honeypot
2019-10-25 15:45:01
1.52.143.168 attackspambots
445/tcp 445/tcp
[2019-10-25]2pkt
2019-10-25 15:17:15
187.114.150.45 attack
Automatic report - Port Scan Attack
2019-10-25 15:16:03
88.210.29.9 attackspam
Chat Spam
2019-10-25 15:37:30
123.27.62.6 attack
Trying to (more than 3 packets) bruteforce (not open) Samba/Microsoft-DS port 445
2019-10-25 15:42:13
182.244.140.34 attackspam
23/tcp
[2019-10-25]1pkt
2019-10-25 15:55:27

Recently Reported IPs

29.199.184.235 118.5.27.165 76.93.78.98 44.41.233.140
52.115.200.121 66.125.80.90 182.167.88.178 65.118.217.23
155.84.51.6 194.14.114.147 201.252.157.87 135.147.161.199
42.209.9.2 207.53.29.117 8.186.194.245 205.248.27.215
42.82.128.18 113.75.193.206 185.131.85.30 42.125.188.106