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 Kingdom of Great Britain and Northern Ireland (the)

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

;; QUESTION SECTION:
;80.2.110.159.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 04:00:28 CST 2025
;; MSG SIZE  rcvd: 105
Host info
159.110.2.80.in-addr.arpa domain name pointer york-06-b2-v4wan-167893-cust1694.vm25.cable.virginm.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
159.110.2.80.in-addr.arpa	name = york-06-b2-v4wan-167893-cust1694.vm25.cable.virginm.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
202.137.134.57 attackspam
suspicious action Wed, 04 Mar 2020 10:37:01 -0300
2020-03-04 22:43:06
196.52.43.105 attack
03/04/2020-08:36:52.730133 196.52.43.105 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-03-04 22:55:55
94.102.56.181 attack
Mar  4 14:37:08 debian-2gb-nbg1-2 kernel: \[5588202.130611\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.56.181 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=20178 PROTO=TCP SPT=40386 DPT=5008 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-04 22:29:13
158.140.136.7 attack
23/tcp
[2020-03-04]1pkt
2020-03-04 22:53:40
139.210.37.78 attackspam
3389/tcp 3389/tcp
[2020-02-28/03-04]2pkt
2020-03-04 22:26:01
14.237.217.158 attackspambots
Honeypot attack, port: 445, PTR: static.vnpt.vn.
2020-03-04 22:57:54
116.49.59.207 attackbotsspam
Honeypot attack, port: 5555, PTR: n1164959207.netvigator.com.
2020-03-04 22:37:29
222.186.31.83 attackbotsspam
Mar  4 15:35:25 debian64 sshd[3357]: Failed password for root from 222.186.31.83 port 63925 ssh2
Mar  4 15:35:29 debian64 sshd[3357]: Failed password for root from 222.186.31.83 port 63925 ssh2
...
2020-03-04 22:45:29
103.83.157.161 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-04 22:19:53
203.152.196.239 attackspam
Honeypot attack, port: 445, PTR: 203.152.196.239.static.zoot.jp.
2020-03-04 22:32:33
144.217.161.78 attack
Mar  4 15:22:03 lnxweb61 sshd[3505]: Failed password for news from 144.217.161.78 port 55176 ssh2
Mar  4 15:22:03 lnxweb61 sshd[3505]: Failed password for news from 144.217.161.78 port 55176 ssh2
2020-03-04 22:54:05
221.180.141.5 attack
$f2bV_matches
2020-03-04 23:02:14
52.246.161.60 attack
Mar  4 04:26:42 hpm sshd\[8401\]: Invalid user robot from 52.246.161.60
Mar  4 04:26:42 hpm sshd\[8401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.246.161.60
Mar  4 04:26:44 hpm sshd\[8401\]: Failed password for invalid user robot from 52.246.161.60 port 55588 ssh2
Mar  4 04:36:26 hpm sshd\[9193\]: Invalid user hl2dm from 52.246.161.60
Mar  4 04:36:26 hpm sshd\[9193\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.246.161.60
2020-03-04 22:38:51
202.137.134.39 attackspam
suspicious action Wed, 04 Mar 2020 10:37:12 -0300
2020-03-04 22:23:24
221.193.253.111 attackspam
$f2bV_matches
2020-03-04 22:55:17

Recently Reported IPs

189.240.140.208 82.149.160.168 95.124.233.26 2.166.91.108
67.95.105.114 89.178.95.144 7.21.27.109 85.75.107.251
53.91.47.101 249.59.97.23 5.131.30.42 33.238.206.59
195.229.171.112 45.204.73.228 176.203.1.208 186.70.62.220
84.1.43.90 199.170.107.155 244.24.248.180 123.138.90.126