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

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

;; QUESTION SECTION:
;80.202.222.42.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 06:01:59 CST 2025
;; MSG SIZE  rcvd: 106
Host info
42.222.202.80.in-addr.arpa domain name pointer 42.80-202-222.nextgentel.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.222.202.80.in-addr.arpa	name = 42.80-202-222.nextgentel.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.216.209.40 attackspambots
Jun 28 10:40:03 dhoomketu sshd[1094281]: Invalid user cacheusr from 178.216.209.40 port 41102
Jun 28 10:40:03 dhoomketu sshd[1094281]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.216.209.40 
Jun 28 10:40:03 dhoomketu sshd[1094281]: Invalid user cacheusr from 178.216.209.40 port 41102
Jun 28 10:40:05 dhoomketu sshd[1094281]: Failed password for invalid user cacheusr from 178.216.209.40 port 41102 ssh2
Jun 28 10:44:24 dhoomketu sshd[1094376]: Invalid user smbuser from 178.216.209.40 port 35812
...
2020-06-28 13:32:48
160.153.156.136 attackspam
C2,WP GET /news/wp-includes/wlwmanifest.xml
2020-06-28 13:34:03
185.2.140.155 attackspam
$f2bV_matches
2020-06-28 13:51:01
207.154.235.23 attack
2020-06-28T05:38:13.017053shield sshd\[26915\]: Invalid user conectar from 207.154.235.23 port 37404
2020-06-28T05:38:13.022802shield sshd\[26915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.235.23
2020-06-28T05:38:15.396105shield sshd\[26915\]: Failed password for invalid user conectar from 207.154.235.23 port 37404 ssh2
2020-06-28T05:41:44.465971shield sshd\[27762\]: Invalid user yuyang from 207.154.235.23 port 37388
2020-06-28T05:41:44.469541shield sshd\[27762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.235.23
2020-06-28 13:47:29
61.177.172.128 attackspambots
Jun 28 07:37:24 server sshd[37149]: Failed none for root from 61.177.172.128 port 24778 ssh2
Jun 28 07:37:27 server sshd[37149]: Failed password for root from 61.177.172.128 port 24778 ssh2
Jun 28 07:37:32 server sshd[37149]: Failed password for root from 61.177.172.128 port 24778 ssh2
2020-06-28 13:44:28
14.98.213.14 attackbotsspam
Jun 27 22:13:12 mockhub sshd[26251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.98.213.14
Jun 27 22:13:14 mockhub sshd[26251]: Failed password for invalid user debian from 14.98.213.14 port 49620 ssh2
...
2020-06-28 13:48:58
212.102.33.47 attack
(From stubbs.alejandro@outlook.com) Hello,

I’m David Domine, owner of Louisville Historic Tours that operates here in Old Louisville, Kentucky.  
Like many businesses, I’m sure you and your employees have probably been stuck at home because of the Kentucky-wide lockdown. Most restaurants and bars still aren’t accepting large groups. This is making get-togethers or outside team building exercises currently impossible. 

That’s why I’m reaching out today.  I run a Daytime Walking Tour and a Nighttime Ghost Tour right here in Louisville.  Since our tours are outside, we are operating fully, and we are able to take groups of people (as long as we follow the social distancing guidelines.)

I’ve had a huge increase in the amount of organizations booking private tours for their employees since everyone is looking for a way to get together.  I wanted to reach out to you about the same possibility.    

Here’s the Daytime Walking Tour:

https://bit.ly/DaytimeWalkingTour

And here’s a bit of detail on the
2020-06-28 13:36:05
104.129.195.4 attack
Jun 28 06:46:38 pkdns2 sshd\[43548\]: Invalid user centos from 104.129.195.4Jun 28 06:46:40 pkdns2 sshd\[43548\]: Failed password for invalid user centos from 104.129.195.4 port 65021 ssh2Jun 28 06:49:49 pkdns2 sshd\[43710\]: Invalid user sendmail from 104.129.195.4Jun 28 06:49:51 pkdns2 sshd\[43710\]: Failed password for invalid user sendmail from 104.129.195.4 port 64631 ssh2Jun 28 06:52:54 pkdns2 sshd\[43880\]: Failed password for root from 104.129.195.4 port 14266 ssh2Jun 28 06:55:55 pkdns2 sshd\[44034\]: Invalid user ark from 104.129.195.4
...
2020-06-28 13:17:03
106.53.75.42 attackspam
Invalid user ts3 from 106.53.75.42 port 43264
2020-06-28 13:21:34
40.85.167.147 attackbots
2020-06-27T22:41:44.890576ns386461 sshd\[6821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.85.167.147  user=root
2020-06-27T22:41:47.273229ns386461 sshd\[6821\]: Failed password for root from 40.85.167.147 port 40809 ssh2
2020-06-28T01:49:12.610016ns386461 sshd\[15969\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.85.167.147  user=root
2020-06-28T01:49:14.148044ns386461 sshd\[15969\]: Failed password for root from 40.85.167.147 port 59941 ssh2
2020-06-28T07:40:25.547745ns386461 sshd\[13567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.85.167.147  user=root
...
2020-06-28 13:53:38
222.186.190.14 attackbotsspam
06/28/2020-01:13:42.580631 222.186.190.14 Protocol: 6 ET SCAN Potential SSH Scan
2020-06-28 13:30:51
49.232.161.242 attackbots
Jun 28 06:55:17 root sshd[11035]: Invalid user richa from 49.232.161.242
...
2020-06-28 13:50:01
222.186.31.83 attack
Jun 28 07:19:20 vps sshd[923721]: Failed password for root from 222.186.31.83 port 28943 ssh2
Jun 28 07:19:22 vps sshd[923721]: Failed password for root from 222.186.31.83 port 28943 ssh2
Jun 28 07:28:26 vps sshd[967113]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83  user=root
Jun 28 07:28:28 vps sshd[967113]: Failed password for root from 222.186.31.83 port 59324 ssh2
Jun 28 07:28:30 vps sshd[967113]: Failed password for root from 222.186.31.83 port 59324 ssh2
...
2020-06-28 13:31:53
194.26.29.32 attack
Jun 28 07:28:28 debian-2gb-nbg1-2 kernel: \[15580757.513461\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.26.29.32 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54988 PROTO=TCP SPT=47643 DPT=5769 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-28 13:43:34
151.236.59.142 attack
Jun 27 18:09:00 php1 sshd\[1041\]: Invalid user bbb from 151.236.59.142
Jun 27 18:09:00 php1 sshd\[1041\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.236.59.142
Jun 27 18:09:02 php1 sshd\[1041\]: Failed password for invalid user bbb from 151.236.59.142 port 45708 ssh2
Jun 27 18:12:13 php1 sshd\[1514\]: Invalid user nti from 151.236.59.142
Jun 27 18:12:13 php1 sshd\[1514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.236.59.142
2020-06-28 13:23:53

Recently Reported IPs

157.173.237.220 216.198.86.177 214.37.195.149 153.13.175.147
41.85.107.195 251.224.63.75 135.222.127.81 21.160.195.252
191.200.218.245 218.92.102.88 199.113.205.104 140.184.211.42
120.179.80.239 164.173.192.235 240.48.54.14 20.56.51.136
202.145.165.97 36.130.55.98 19.112.131.174 235.100.139.43