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

;; QUESTION SECTION:
;254.53.70.16.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 22:02:53 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 16.70.53.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 16.70.53.254.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
122.195.200.148 attackspambots
Jul 18 02:09:14 ncomp sshd[15728]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.195.200.148  user=root
Jul 18 02:09:16 ncomp sshd[15728]: Failed password for root from 122.195.200.148 port 35632 ssh2
Jul 18 02:09:25 ncomp sshd[15735]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.195.200.148  user=root
Jul 18 02:09:26 ncomp sshd[15735]: Failed password for root from 122.195.200.148 port 16770 ssh2
2019-07-18 08:09:30
162.243.139.8 attackbots
8140/tcp 1400/tcp 5903/tcp...
[2019-05-18/07-15]59pkt,47pt.(tcp),5pt.(udp),1proto
2019-07-18 08:14:09
203.114.102.69 attackspam
Jul 18 06:36:49 webhost01 sshd[9422]: Failed password for root from 203.114.102.69 port 39502 ssh2
Jul 18 06:42:20 webhost01 sshd[9486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.102.69
...
2019-07-18 07:49:27
186.228.60.22 attackspam
Jul 18 02:11:45 mail sshd\[13151\]: Invalid user helpdesk from 186.228.60.22 port 47476
Jul 18 02:11:45 mail sshd\[13151\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.228.60.22
Jul 18 02:11:48 mail sshd\[13151\]: Failed password for invalid user helpdesk from 186.228.60.22 port 47476 ssh2
Jul 18 02:17:37 mail sshd\[14055\]: Invalid user guest from 186.228.60.22 port 53935
Jul 18 02:17:37 mail sshd\[14055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.228.60.22
2019-07-18 08:26:54
117.239.66.74 attack
Scanning random ports - tries to find possible vulnerable services
2019-07-18 07:56:39
159.89.231.161 attackbots
2019-07-17T16:59:01.546411Z 5b647e8bc805 New connection: 159.89.231.161:54126 (172.17.0.4:2222) [session: 5b647e8bc805]
2019-07-17T16:59:21.549011Z 03d9e59e3f58 New connection: 159.89.231.161:49352 (172.17.0.4:2222) [session: 03d9e59e3f58]
2019-07-18 07:45:53
185.181.100.183 attackbotsspam
Unauthorized access detected from banned ip
2019-07-18 08:13:43
104.144.45.176 attackspambots
(From edingram151@gmail.com) Greetings!

Are you satisfied of the number of sales you're able to generate from your site? How many of your clients found your business while they were searching on the internet? I'm a freelancer looking for new clients that are open for new opportunities for business growth through search engine marketing. I ran some search traffic reports on your website and results showed that there's a great amount of additional traffic that I can get for you by fixing a few issues on your site which later gets you into higher positions in web searches. You won't have to worry about my fees since I'm a freelancer who can deliver excellent results at a price that even the smallest businesses consider cheap.

If you'd like to find out more about how SEO can help your business, then please let me know so we can set up a time for a consultation over the phone. The info I'll discuss and give0 to you can benefit your business whether or not you choose to avail of my services. I'd love to speak
2019-07-18 08:12:10
138.197.103.160 attackspambots
Jul 18 01:57:43 OPSO sshd\[15019\]: Invalid user tom from 138.197.103.160 port 36158
Jul 18 01:57:43 OPSO sshd\[15019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.103.160
Jul 18 01:57:44 OPSO sshd\[15019\]: Failed password for invalid user tom from 138.197.103.160 port 36158 ssh2
Jul 18 02:02:15 OPSO sshd\[15594\]: Invalid user backend from 138.197.103.160 port 34464
Jul 18 02:02:15 OPSO sshd\[15594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.103.160
2019-07-18 08:19:56
91.187.123.233 attackspambots
Unauthorised access (Jul 17) SRC=91.187.123.233 LEN=40 TTL=242 ID=51510 TCP DPT=445 WINDOW=1024 SYN
2019-07-18 07:51:54
131.196.7.234 attackbotsspam
Jul 18 01:37:01 bouncer sshd\[22482\]: Invalid user ftp_user from 131.196.7.234 port 49951
Jul 18 01:37:01 bouncer sshd\[22482\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=131.196.7.234 
Jul 18 01:37:03 bouncer sshd\[22482\]: Failed password for invalid user ftp_user from 131.196.7.234 port 49951 ssh2
...
2019-07-18 08:04:04
71.127.39.171 attackspambots
17.07.2019 16:22:24 SSH access blocked by firewall
2019-07-18 08:19:23
162.243.150.140 attackbotsspam
" "
2019-07-18 08:23:39
45.55.142.207 attackbots
Jul 18 02:07:43 legacy sshd[24527]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.142.207
Jul 18 02:07:45 legacy sshd[24527]: Failed password for invalid user avorion from 45.55.142.207 port 57844 ssh2
Jul 18 02:12:19 legacy sshd[24688]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.142.207
...
2019-07-18 08:12:32
160.2.95.199 attack
kp-nj1-01 recorded 6 login violations from 160.2.95.199 and was blocked at 2019-07-17 16:23:16. 160.2.95.199 has been blocked on 0 previous occasions. 160.2.95.199's first attempt was recorded at 2019-07-17 16:23:16
2019-07-18 07:56:07

Recently Reported IPs

173.52.179.40 145.55.194.55 3.228.139.188 199.203.197.91
233.15.142.15 41.200.234.145 156.14.193.37 44.150.204.196
212.26.23.230 179.45.140.40 128.80.87.111 184.162.63.15
212.9.50.53 219.218.109.156 240.108.156.7 83.116.167.156
206.190.172.20 60.151.101.14 91.237.231.208 216.118.234.225