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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;254.199.134.8.			IN	A

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

;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 19:40:00 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 8.134.199.254.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 8.134.199.254.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
38.64.178.194 attackbots
proto=tcp  .  spt=33306  .  dpt=25  .     (listed on Blocklist de  Aug 04)     (702)
2019-08-05 14:18:14
172.68.46.212 attackbotsspam
Wordpress XMLRPC attack
2019-08-05 14:14:55
179.85.157.30 attack
port scan and connect, tcp 22 (ssh)
2019-08-05 13:18:15
52.166.134.250 attack
Aug  5 06:41:29 root sshd[10765]: Failed password for root from 52.166.134.250 port 57000 ssh2
Aug  5 06:46:15 root sshd[10795]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.166.134.250 
Aug  5 06:46:17 root sshd[10795]: Failed password for invalid user deployer from 52.166.134.250 port 54932 ssh2
...
2019-08-05 13:52:26
91.138.201.202 attackbotsspam
Autoban   91.138.201.202 AUTH/CONNECT
2019-08-05 13:18:32
91.139.1.158 attack
Autoban   91.139.1.158 AUTH/CONNECT
2019-08-05 13:17:35
89.210.157.52 attackbots
Autoban   89.210.157.52 AUTH/CONNECT
2019-08-05 14:03:45
121.160.21.6 attackbots
Aug  5 00:47:19 sshgateway sshd\[20050\]: Invalid user HDP from 121.160.21.6
Aug  5 00:47:19 sshgateway sshd\[20050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.160.21.6
Aug  5 00:47:21 sshgateway sshd\[20050\]: Failed password for invalid user HDP from 121.160.21.6 port 56712 ssh2
2019-08-05 14:16:59
91.106.42.20 attack
Autoban   91.106.42.20 AUTH/CONNECT
2019-08-05 13:25:29
89.64.3.247 attack
Autoban   89.64.3.247 AUTH/CONNECT
2019-08-05 13:45:17
91.139.50.102 attackbotsspam
Autoban   91.139.50.102 AUTH/CONNECT
2019-08-05 13:16:51
89.23.162.211 attackspambots
Autoban   89.23.162.211 AUTH/CONNECT
2019-08-05 13:58:35
89.153.25.60 attackbots
Autoban   89.153.25.60 AUTH/CONNECT
2019-08-05 14:15:22
89.23.163.183 attackspambots
Autoban   89.23.163.183 AUTH/CONNECT
2019-08-05 13:55:49
5.39.3.235 attackbotsspam
Jan  3 17:25:58 motanud sshd\[14469\]: Invalid user jira from 5.39.3.235 port 40090
Jan  3 17:25:58 motanud sshd\[14469\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.3.235
Jan  3 17:26:00 motanud sshd\[14469\]: Failed password for invalid user jira from 5.39.3.235 port 40090 ssh2
2019-08-05 14:04:39

Recently Reported IPs

68.187.252.35 81.103.246.219 8.137.166.201 99.106.153.164
2.137.60.13 63.132.11.116 223.4.186.6 75.161.228.138
95.211.168.160 241.160.45.39 41.53.143.153 68.61.222.102
173.137.86.154 236.255.59.197 177.214.66.7 101.49.223.114
199.182.209.10 168.217.147.178 211.14.241.56 108.91.211.204