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

Region: Päijänne Tavastia

Country: Finland

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:
IP Type Details Datetime
80.64.132.8 attackspam
80.64.132.8 - - [05/Aug/2020:17:18:43 +0200] "POST /wp-login.php HTTP/1.1" 200 3434 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-08-05 23:46:13
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.64.13.199
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31766
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;80.64.13.199.			IN	A

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

;; Query time: 102 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 02 20:42:25 CST 2020
;; MSG SIZE  rcvd: 116
Host info
199.13.64.80.in-addr.arpa has no PTR record
Nslookup info:
;; Got SERVFAIL reply from 183.60.82.98, trying next server
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 199.13.64.80.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
193.188.23.21 attack
Unauthorized connection attempt detected from IP address 193.188.23.21 to port 3376
2020-01-06 05:31:13
77.42.86.162 attackbotsspam
Unauthorized connection attempt detected from IP address 77.42.86.162 to port 2323 [J]
2020-01-06 05:45:05
188.217.231.74 attackbotsspam
Unauthorized connection attempt detected from IP address 188.217.231.74 to port 23 [J]
2020-01-06 05:32:24
49.234.6.105 attackbotsspam
Jan  5 22:46:31 srv01 sshd[31571]: Invalid user test12 from 49.234.6.105 port 33712
Jan  5 22:46:31 srv01 sshd[31571]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.6.105
Jan  5 22:46:31 srv01 sshd[31571]: Invalid user test12 from 49.234.6.105 port 33712
Jan  5 22:46:33 srv01 sshd[31571]: Failed password for invalid user test12 from 49.234.6.105 port 33712 ssh2
Jan  5 22:49:29 srv01 sshd[31796]: Invalid user jsj from 49.234.6.105 port 56060
...
2020-01-06 06:02:20
180.76.134.246 attack
Unauthorized connection attempt detected from IP address 180.76.134.246 to port 2220 [J]
2020-01-06 05:59:10
103.129.64.150 attackbotsspam
Unauthorized connection attempt detected from IP address 103.129.64.150 to port 23 [J]
2020-01-06 05:59:51
66.240.192.138 attackspambots
Unauthorized connection attempt detected from IP address 66.240.192.138 to port 8099
2020-01-06 05:45:49
212.171.220.200 attackbotsspam
Unauthorized connection attempt detected from IP address 212.171.220.200 to port 5555
2020-01-06 05:27:18
34.215.69.55 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2020-01-06 06:02:41
112.186.145.105 attackbots
Unauthorized connection attempt detected from IP address 112.186.145.105 to port 4567 [J]
2020-01-06 05:38:01
110.49.70.243 attackspam
detected by Fail2Ban
2020-01-06 06:04:13
111.38.216.94 attack
SSH bruteforce
2020-01-06 05:57:05
104.200.110.184 attackbots
Unauthorized connection attempt detected from IP address 104.200.110.184 to port 2220 [J]
2020-01-06 05:55:50
211.38.189.134 attackspam
Unauthorized connection attempt detected from IP address 211.38.189.134 to port 5555 [J]
2020-01-06 05:28:28
212.104.168.11 attackspam
Honeypot attack, port: 81, PTR: PTR record not found
2020-01-06 05:58:23

Recently Reported IPs

174.234.45.242 148.5.50.235 221.105.196.205 218.166.149.52
63.43.243.56 58.89.87.169 111.141.138.147 152.192.65.243
214.249.169.228 20.162.131.84 63.249.94.237 154.126.237.90
54.202.169.92 221.36.55.74 5.45.142.127 198.151.234.201
32.172.161.186 50.249.122.110 44.32.172.138 180.76.104.167