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

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

;; QUESTION SECTION:
;40.4.80.68.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 03 16:33:44 CST 2025
;; MSG SIZE  rcvd: 103
Host info
Host 68.80.4.40.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 68.80.4.40.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
212.30.52.243 attackbots
Nov 10 09:39:28 root sshd[24640]: Failed password for root from 212.30.52.243 port 42735 ssh2
Nov 10 09:43:30 root sshd[24693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.30.52.243 
Nov 10 09:43:32 root sshd[24693]: Failed password for invalid user jill from 212.30.52.243 port 33654 ssh2
...
2019-11-10 17:53:50
106.54.239.60 attackspambots
Nov 10 10:18:48 ns41 sshd[30114]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.239.60
2019-11-10 17:37:29
61.183.178.194 attackbots
Nov 10 10:10:09 localhost sshd\[1152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194  user=root
Nov 10 10:10:12 localhost sshd\[1152\]: Failed password for root from 61.183.178.194 port 4075 ssh2
Nov 10 10:15:03 localhost sshd\[1607\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194  user=root
2019-11-10 17:20:15
178.128.52.97 attackbotsspam
CyberHackers.eu > SSH Bruteforce attempt!
2019-11-10 17:39:18
159.203.83.37 attackbotsspam
Failed password for root from 159.203.83.37 port 45453 ssh2
Invalid user before from 159.203.83.37 port 33964
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.83.37
Failed password for invalid user before from 159.203.83.37 port 33964 ssh2
Invalid user bahuvidha from 159.203.83.37 port 50707
2019-11-10 17:47:18
167.179.69.206 attackbotsspam
Nov  9 20:15:05 shadeyouvpn sshd[24359]: Address 167.179.69.206 maps to 167.179.69.206.vultr.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  9 20:15:05 shadeyouvpn sshd[24359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.179.69.206  user=r.r
Nov  9 20:15:07 shadeyouvpn sshd[24359]: Failed password for r.r from 167.179.69.206 port 49706 ssh2
Nov  9 20:15:07 shadeyouvpn sshd[24359]: Received disconnect from 167.179.69.206: 11: Bye Bye [preauth]
Nov  9 20:35:16 shadeyouvpn sshd[5281]: Address 167.179.69.206 maps to 167.179.69.206.vultr.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  9 20:35:16 shadeyouvpn sshd[5281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.179.69.206  user=r.r
Nov  9 20:35:18 shadeyouvpn sshd[5281]: Failed password for r.r from 167.179.69.206 port 60256 ssh2
Nov  9 20:35:18 shadeyouvpn sshd[52........
-------------------------------
2019-11-10 17:28:39
220.202.75.199 attackbotsspam
Nov  8 07:47:26 CT721 postfix/smtpd[2954]: connect from unknown[220.202.75.199]
Nov  8 07:47:29 CT721 postfix/smtpd[2954]: warning: unknown[220.202.75.199]: SASL LOGIN authentication failed: authentication failure
Nov  8 07:47:29 CT721 postfix/smtpd[2954]: disconnect from unknown[220.202.75.199]
Nov  8 07:47:41 CT721 postfix/smtpd[2954]: connect from unknown[220.202.75.199]
Nov  8 07:47:42 CT721 postfix/smtpd[2954]: warning: unknown[220.202.75.199]: SASL LOGIN authentication failed: authentication failure
Nov  8 07:47:43 CT721 postfix/smtpd[2954]: disconnect from unknown[220.202.75.199]
Nov  8 07:47:45 CT721 postfix/smtpd[2954]: connect from unknown[220.202.75.199]
Nov  8 07:47:47 CT721 postfix/smtpd[2954]: warning: unknown[220.202.75.199]: SASL LOGIN authentication failed: authentication failure
Nov  8 07:47:47 CT721 postfix/smtpd[2954]: disconnect from unknown[220.202.75.199]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=220.202.75.199
2019-11-10 17:17:37
222.186.175.216 attackbots
SSH Brute-Force reported by Fail2Ban
2019-11-10 17:35:06
125.177.17.175 attack
Nov 10 07:45:22 vpn01 sshd[24669]: Failed password for root from 125.177.17.175 port 48002 ssh2
...
2019-11-10 17:37:05
1.119.150.195 attack
Nov 10 04:00:35 Tower sshd[14035]: Connection from 1.119.150.195 port 55909 on 192.168.10.220 port 22
Nov 10 04:00:36 Tower sshd[14035]: Failed password for root from 1.119.150.195 port 55909 ssh2
Nov 10 04:00:36 Tower sshd[14035]: Received disconnect from 1.119.150.195 port 55909:11: Bye Bye [preauth]
Nov 10 04:00:36 Tower sshd[14035]: Disconnected from authenticating user root 1.119.150.195 port 55909 [preauth]
2019-11-10 17:40:34
132.232.59.247 attackbots
$f2bV_matches
2019-11-10 17:16:59
139.59.41.154 attack
Nov 10 10:37:40 SilenceServices sshd[18969]: Failed password for root from 139.59.41.154 port 60920 ssh2
Nov 10 10:41:47 SilenceServices sshd[20316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Nov 10 10:41:49 SilenceServices sshd[20316]: Failed password for invalid user kaushik from 139.59.41.154 port 49814 ssh2
2019-11-10 17:48:48
186.189.134.55 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/186.189.134.55/ 
 
 AW - 1H : (1)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : AW 
 NAME ASN : ASN11816 
 
 IP : 186.189.134.55 
 
 CIDR : 186.189.134.0/23 
 
 PREFIX COUNT : 115 
 
 UNIQUE IP COUNT : 100608 
 
 
 ATTACKS DETECTED ASN11816 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-10 07:28:18 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-10 17:54:12
182.61.133.172 attackspam
Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: Invalid user 123 from 182.61.133.172
Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.172
Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: Invalid user 123 from 182.61.133.172
Nov 10 10:00:28 srv-ubuntu-dev3 sshd[2950]: Failed password for invalid user 123 from 182.61.133.172 port 36856 ssh2
Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: Invalid user P@55W0rd from 182.61.133.172
Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.172
Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: Invalid user P@55W0rd from 182.61.133.172
Nov 10 10:05:29 srv-ubuntu-dev3 sshd[3388]: Failed password for invalid user P@55W0rd from 182.61.133.172 port 44234 ssh2
Nov 10 10:10:25 srv-ubuntu-dev3 sshd[3970]: Invalid user rootCAV from 182.61.133.172
...
2019-11-10 17:34:38
198.108.66.80 attackbots
SMTP:25. Blocked 3 login attempts in 301 days.
2019-11-10 17:16:07

Recently Reported IPs

219.223.196.141 50.43.147.95 251.137.202.211 193.93.180.213
149.167.2.252 122.250.176.11 125.52.148.176 38.73.85.163
134.160.227.119 165.172.196.220 2.156.239.73 217.249.76.59
52.177.222.207 246.184.237.168 57.166.22.184 173.39.195.39
174.17.229.21 243.225.57.179 98.201.181.106 232.116.48.132