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: Germany

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

;; QUESTION SECTION:
;80.142.140.192.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 11:06:54 CST 2025
;; MSG SIZE  rcvd: 107
Host info
192.140.142.80.in-addr.arpa domain name pointer p508e8cc0.dip0.t-ipconnect.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
192.140.142.80.in-addr.arpa	name = p508e8cc0.dip0.t-ipconnect.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
128.199.162.108 attack
2019-11-17T05:07:08.928046shield sshd\[13180\]: Invalid user sumiko from 128.199.162.108 port 52628
2019-11-17T05:07:08.932173shield sshd\[13180\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.162.108
2019-11-17T05:07:11.404335shield sshd\[13180\]: Failed password for invalid user sumiko from 128.199.162.108 port 52628 ssh2
2019-11-17T05:11:09.205970shield sshd\[14038\]: Invalid user rpm from 128.199.162.108 port 60990
2019-11-17T05:11:09.210813shield sshd\[14038\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.162.108
2019-11-17 14:27:00
51.75.169.236 attackspam
Nov 17 07:47:22 vps666546 sshd\[22257\]: Invalid user mercure from 51.75.169.236 port 46340
Nov 17 07:47:22 vps666546 sshd\[22257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.169.236
Nov 17 07:47:23 vps666546 sshd\[22257\]: Failed password for invalid user mercure from 51.75.169.236 port 46340 ssh2
Nov 17 07:50:53 vps666546 sshd\[22341\]: Invalid user guest12346 from 51.75.169.236 port 36688
Nov 17 07:50:53 vps666546 sshd\[22341\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.169.236
...
2019-11-17 14:55:50
117.6.199.89 attackspambots
SpamReport
2019-11-17 14:42:56
117.70.39.249 attack
badbot
2019-11-17 14:23:30
109.237.212.66 attack
Nov 17 07:19:53 Invalid user clinckspoor from 109.237.212.66 port 50774
2019-11-17 14:43:39
37.59.58.142 attackbotsspam
Invalid user siaud from 37.59.58.142 port 60164
2019-11-17 14:06:50
119.28.105.127 attackspambots
Nov 17 06:41:55 game-panel sshd[18726]: Failed password for root from 119.28.105.127 port 57870 ssh2
Nov 17 06:47:51 game-panel sshd[18957]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.105.127
Nov 17 06:47:54 game-panel sshd[18957]: Failed password for invalid user mccord from 119.28.105.127 port 36888 ssh2
2019-11-17 14:49:43
189.163.157.56 attack
Automatic report - Port Scan Attack
2019-11-17 14:18:25
46.38.144.17 attack
Nov 17 07:43:23 relay postfix/smtpd\[10540\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 17 07:43:41 relay postfix/smtpd\[19666\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 17 07:44:01 relay postfix/smtpd\[21176\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 17 07:44:20 relay postfix/smtpd\[10090\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 17 07:44:38 relay postfix/smtpd\[22590\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-17 14:46:48
193.91.125.249 attackbotsspam
Automatic report - Banned IP Access
2019-11-17 14:21:33
218.57.90.40 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/218.57.90.40/ 
 
 CN - 1H : (668)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4837 
 
 IP : 218.57.90.40 
 
 CIDR : 218.57.0.0/17 
 
 PREFIX COUNT : 1262 
 
 UNIQUE IP COUNT : 56665856 
 
 
 ATTACKS DETECTED ASN4837 :  
  1H - 6 
  3H - 34 
  6H - 69 
 12H - 130 
 24H - 245 
 
 DateTime : 2019-11-17 05:56:51 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-17 14:17:31
185.76.34.87 attackspam
Invalid user ts3user from 185.76.34.87 port 52932
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87
Failed password for invalid user ts3user from 185.76.34.87 port 52932 ssh2
Invalid user guest from 185.76.34.87 port 60976
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.76.34.87
2019-11-17 14:12:31
95.46.8.176 attack
Nov 17 07:42:26 eventyay sshd[23696]: Failed password for root from 95.46.8.176 port 58128 ssh2
Nov 17 07:47:38 eventyay sshd[23767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.46.8.176
Nov 17 07:47:40 eventyay sshd[23767]: Failed password for invalid user almeta from 95.46.8.176 port 43888 ssh2
...
2019-11-17 14:51:43
63.240.240.74 attackspambots
Triggered by Fail2Ban at Vostok web server
2019-11-17 14:51:05
74.208.252.144 attackbotsspam
Automatic report - XMLRPC Attack
2019-11-17 14:53:30

Recently Reported IPs

24.122.106.42 39.152.21.221 146.100.119.82 93.52.52.223
138.116.52.26 138.254.35.116 34.141.180.185 96.91.54.178
167.174.253.3 109.181.154.65 180.66.144.83 175.74.75.120
119.117.3.229 48.46.69.133 191.100.126.231 8.22.103.228
243.65.47.208 185.236.208.188 64.38.127.164 250.254.254.236