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

;; QUESTION SECTION:
;2.214.71.80.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 09 08:33:02 CST 2022
;; MSG SIZE  rcvd: 104
Host info
80.71.214.2.in-addr.arpa domain name pointer dynamic-002-214-071-080.2.214.pool.telefonica.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.71.214.2.in-addr.arpa	name = dynamic-002-214-071-080.2.214.pool.telefonica.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
66.249.73.155 attackbotsspam
Automatic report - Banned IP Access
2019-08-09 14:09:19
188.166.70.245 attack
Automatic report - Banned IP Access
2019-08-09 14:16:36
35.246.244.55 attackspam
Triggered by Fail2Ban at Vostok web server
2019-08-09 14:42:40
93.147.41.212 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-09 14:25:40
91.211.228.14 attackbotsspam
[portscan] Port scan
2019-08-09 14:41:46
52.179.138.240 attackspam
RDP Bruteforce
2019-08-09 13:58:33
37.49.227.92 attackbotsspam
$f2bV_matches
2019-08-09 14:01:17
185.143.223.8 attack
Port scan attempt detected by AWS-CCS, CTS, India
2019-08-09 14:44:35
178.128.215.16 attack
Unauthorized SSH login attempts
2019-08-09 14:02:04
39.66.11.9 attack
Aug  8 17:23:49 eola postfix/smtpd[5461]: connect from unknown[39.66.11.9]
Aug  8 17:23:50 eola postfix/smtpd[5461]: lost connection after AUTH from unknown[39.66.11.9]
Aug  8 17:23:50 eola postfix/smtpd[5461]: disconnect from unknown[39.66.11.9] ehlo=1 auth=0/1 commands=1/2
Aug  8 17:24:01 eola postfix/smtpd[5461]: connect from unknown[39.66.11.9]
Aug  8 17:24:02 eola postfix/smtpd[5461]: lost connection after AUTH from unknown[39.66.11.9]
Aug  8 17:24:02 eola postfix/smtpd[5461]: disconnect from unknown[39.66.11.9] ehlo=1 auth=0/1 commands=1/2
Aug  8 17:24:10 eola postfix/smtpd[5461]: connect from unknown[39.66.11.9]
Aug  8 17:24:11 eola postfix/smtpd[5461]: lost connection after AUTH from unknown[39.66.11.9]
Aug  8 17:24:11 eola postfix/smtpd[5461]: disconnect from unknown[39.66.11.9] ehlo=1 auth=0/1 commands=1/2
Aug  8 17:24:13 eola postfix/smtpd[6563]: connect from unknown[39.66.11.9]
Aug  8 17:24:14 eola postfix/smtpd[6563]: lost connection after AUTH from unknown........
-------------------------------
2019-08-09 14:06:35
122.226.181.167 attackspambots
fire
2019-08-09 14:11:57
218.92.0.173 attack
Aug  9 03:30:26 *** sshd[12523]: User root from 218.92.0.173 not allowed because not listed in AllowUsers
2019-08-09 14:08:10
122.226.181.165 attackbotsspam
fire
2019-08-09 14:22:07
43.225.20.172 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-09 14:33:33
202.100.182.250 attack
Aug  8 16:41:39 oldtbh2 sshd[23548]: Failed unknown for invalid user admin from 202.100.182.250 port 40898 ssh2
Aug  8 16:41:39 oldtbh2 sshd[23548]: Failed unknown for invalid user admin from 202.100.182.250 port 40898 ssh2
Aug  8 16:41:40 oldtbh2 sshd[23548]: Failed unknown for invalid user admin from 202.100.182.250 port 40898 ssh2
...
2019-08-09 14:16:15

Recently Reported IPs

26.169.18.225 39.110.229.214 248.89.53.50 110.156.91.188
172.202.97.42 190.88.173.18 199.195.190.238 124.218.34.234
148.69.27.3 176.180.232.50 255.246.229.97 217.201.216.202
6.233.115.166 115.11.223.232 5.187.86.203 149.147.114.251
9.96.254.36 142.250.75.4 142.142.230.179 219.20.4.191