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

;; QUESTION SECTION:
;54.68.4.105.			IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 19 19:32:17 CST 2025
;; MSG SIZE  rcvd: 104
Host info
105.4.68.54.in-addr.arpa domain name pointer ec2-54-68-4-105.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
105.4.68.54.in-addr.arpa	name = ec2-54-68-4-105.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
209.17.96.114 attack
The IP has triggered Cloudflare WAF. CF-Ray: 54f18c36bf2fba46 | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: blog.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: ATL. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2020-01-04 03:30:49
46.105.124.219 attackbotsspam
Jan  4 01:47:55 webhost01 sshd[23310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.124.219
Jan  4 01:47:57 webhost01 sshd[23310]: Failed password for invalid user nasa from 46.105.124.219 port 48058 ssh2
...
2020-01-04 03:52:30
189.112.228.153 attackbots
Jan  3 21:44:28 main sshd[2164]: Failed password for invalid user mitchell from 189.112.228.153 port 58037 ssh2
2020-01-04 04:06:23
191.235.91.156 attackspambots
Jan  3 19:47:13 powerpi2 sshd[12593]: Invalid user ve from 191.235.91.156 port 54770
Jan  3 19:47:16 powerpi2 sshd[12593]: Failed password for invalid user ve from 191.235.91.156 port 54770 ssh2
Jan  3 19:53:59 powerpi2 sshd[12946]: Invalid user service from 191.235.91.156 port 58438
...
2020-01-04 04:05:48
45.123.92.1 attack
Input Traffic from this IP, but critial abuseconfidencescore
2020-01-04 03:58:08
51.89.173.198 attackspambots
SMTP:25. Blocked login attempt.
2020-01-04 03:29:28
190.64.137.171 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-01-04 03:39:28
203.113.25.6 attackspam
Tried sshing with brute force.
2020-01-04 03:35:52
119.206.86.8 attack
Jan  3 12:59:18 system,error,critical: login failure for user admin from 119.206.86.8 via telnet
Jan  3 12:59:20 system,error,critical: login failure for user root from 119.206.86.8 via telnet
Jan  3 12:59:21 system,error,critical: login failure for user admin from 119.206.86.8 via telnet
Jan  3 12:59:26 system,error,critical: login failure for user root from 119.206.86.8 via telnet
Jan  3 12:59:28 system,error,critical: login failure for user root from 119.206.86.8 via telnet
Jan  3 12:59:30 system,error,critical: login failure for user admin from 119.206.86.8 via telnet
Jan  3 12:59:35 system,error,critical: login failure for user root from 119.206.86.8 via telnet
Jan  3 12:59:37 system,error,critical: login failure for user root from 119.206.86.8 via telnet
Jan  3 12:59:39 system,error,critical: login failure for user tech from 119.206.86.8 via telnet
Jan  3 12:59:44 system,error,critical: login failure for user service from 119.206.86.8 via telnet
2020-01-04 03:49:20
202.51.116.74 attackspambots
Unauthorized connection attempt detected from IP address 202.51.116.74 to port 445
2020-01-04 03:45:18
203.109.45.228 attackbots
Unauthorized connection attempt from IP address 203.109.45.228 on Port 445(SMB)
2020-01-04 03:30:12
121.229.0.50 attack
Jan  3 11:24:19 web1 postfix/smtpd[3742]: warning: unknown[121.229.0.50]: SASL LOGIN authentication failed: authentication failure
...
2020-01-04 03:55:30
182.61.173.205 attackbots
SSH/22 MH Probe, BF, Hack -
2020-01-04 04:08:40
95.246.99.23 attackbotsspam
Jan  3 14:10:15 vps691689 sshd[27277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.246.99.23
Jan  3 14:10:18 vps691689 sshd[27277]: Failed password for invalid user ubnt from 95.246.99.23 port 34944 ssh2
Jan  3 14:15:24 vps691689 sshd[27326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.246.99.23
...
2020-01-04 03:41:56
209.17.96.250 attack
The IP has triggered Cloudflare WAF. CF-Ray: 54f3e188ff48e760 | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: notes.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: EWR. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2020-01-04 03:29:55

Recently Reported IPs

48.93.122.63 180.97.103.160 65.224.239.252 156.21.85.40
167.113.239.46 58.86.183.35 178.181.43.36 220.7.73.77
146.94.89.235 59.145.125.244 183.54.82.93 83.119.100.44
216.247.140.27 33.42.227.108 74.172.146.148 68.191.190.160
84.252.173.41 58.154.192.229 164.197.106.209 96.105.208.76