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

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

;; QUESTION SECTION:
;80.99.172.12.			IN	A

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

;; Query time: 48 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jun 25 23:23:01 CST 2022
;; MSG SIZE  rcvd: 105
Host info
12.172.99.80.in-addr.arpa domain name pointer catv-80-99-172-12.catv.fixed.vodafone.hu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.172.99.80.in-addr.arpa	name = catv-80-99-172-12.catv.fixed.vodafone.hu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
77.247.110.166 attack
SIPVicious Scanner Detection, PTR: PTR record not found
2019-07-09 19:28:50
51.158.106.49 attackbots
LGS,WP GET /wordpress8/wp-login.php
2019-07-09 18:46:33
206.189.23.43 attackspambots
2019-07-09T08:05:25.812622abusebot-4.cloudsearch.cf sshd\[24721\]: Invalid user tomcat from 206.189.23.43 port 54722
2019-07-09 18:49:31
113.197.207.110 attackspam
Caught in portsentry honeypot
2019-07-09 19:15:59
123.20.112.141 attackbots
Jul  9 06:17:11 srv-4 sshd\[1404\]: Invalid user admin from 123.20.112.141
Jul  9 06:17:11 srv-4 sshd\[1404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.20.112.141
Jul  9 06:17:13 srv-4 sshd\[1404\]: Failed password for invalid user admin from 123.20.112.141 port 51410 ssh2
...
2019-07-09 18:52:01
139.59.59.187 attackbotsspam
Jul  9 12:01:06 XXX sshd[37594]: Invalid user shop from 139.59.59.187 port 38078
2019-07-09 19:10:01
14.139.153.212 attackspambots
Jul  9 06:25:29 localhost sshd\[26627\]: Invalid user dummy from 14.139.153.212 port 44918
Jul  9 06:25:29 localhost sshd\[26627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.139.153.212
Jul  9 06:25:31 localhost sshd\[26627\]: Failed password for invalid user dummy from 14.139.153.212 port 44918 ssh2
Jul  9 06:29:13 localhost sshd\[26749\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.139.153.212  user=root
Jul  9 06:29:15 localhost sshd\[26749\]: Failed password for root from 14.139.153.212 port 53628 ssh2
...
2019-07-09 19:25:19
218.92.0.196 attack
Jul  9 06:17:44 * sshd[15192]: Failed password for root from 218.92.0.196 port 51599 ssh2
2019-07-09 18:48:57
89.248.172.85 attackbotsspam
Jul  9 10:09:09   TCP Attack: SRC=89.248.172.85 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=246  PROTO=TCP SPT=59118 DPT=1986 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-09 19:31:33
1.34.179.14 attack
Telnet/23 MH Probe, BF, Hack -
2019-07-09 18:40:40
165.22.78.120 attackbotsspam
SSH bruteforce
2019-07-09 18:38:13
88.153.128.51 attackbots
SSH Bruteforce
2019-07-09 19:22:02
202.90.134.27 attackbots
Unauthorized connection attempt from IP address 202.90.134.27 on Port 445(SMB)
2019-07-09 19:17:40
200.94.105.39 attackspambots
19/7/8@23:16:52: FAIL: Alarm-Intrusion address from=200.94.105.39
...
2019-07-09 18:57:24
185.134.99.66 attackspambots
email spam
2019-07-09 19:08:49

Recently Reported IPs

115.159.29.89 81.68.127.179 193.233.231.60 81.37.45.10
78.160.155.67 137.226.186.142 182.209.131.142 192.241.222.134
173.184.75.231 5.167.69.167 58.191.191.204 59.10.231.130
82.47.101.156 84.39.180.140 81.203.113.191 81.147.171.115
137.226.60.56 75.117.138.2 118.232.162.108 193.233.137.189