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: South Africa

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

;; QUESTION SECTION:
;102.220.80.194.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 21 20:35:08 CST 2023
;; MSG SIZE  rcvd: 107
Host info
Host 194.80.220.102.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 194.80.220.102.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
112.135.232.170 attack
Attempts against non-existent wp-login
2020-09-09 20:02:14
101.31.140.188 attack
Unauthorised access (Sep  8) SRC=101.31.140.188 LEN=40 TTL=46 ID=31452 TCP DPT=23 WINDOW=30906 SYN
2020-09-09 20:00:00
45.9.148.29 attackbots
Fail2Ban Ban Triggered
2020-09-09 20:28:52
116.193.216.231 attackspam
Port scan on 1 port(s): 445
2020-09-09 20:02:45
217.181.146.185 attackbots
 TCP (SYN) 217.181.146.185:29113 -> port 23, len 44
2020-09-09 19:58:25
122.228.19.79 attackbotsspam
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2020-09-09 19:50:06
54.38.240.23 attackspambots
(sshd) Failed SSH login from 54.38.240.23 (FR/France/23.ip-54-38-240.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  9 01:03:58 server sshd[21142]: Failed password for root from 54.38.240.23 port 58110 ssh2
Sep  9 01:19:01 server sshd[25090]: Invalid user default from 54.38.240.23 port 47366
Sep  9 01:19:03 server sshd[25090]: Failed password for invalid user default from 54.38.240.23 port 47366 ssh2
Sep  9 01:23:06 server sshd[26232]: Invalid user guest from 54.38.240.23 port 53832
Sep  9 01:23:08 server sshd[26232]: Failed password for invalid user guest from 54.38.240.23 port 53832 ssh2
2020-09-09 20:04:52
178.127.223.69 attackspam
mail auth brute force
2020-09-09 20:19:48
185.200.118.74 attack
TCP ports : 1723 / 3128
2020-09-09 19:56:31
118.25.93.240 attackbots
"$f2bV_matches"
2020-09-09 20:16:09
185.132.53.237 attackspam
Sep  9 13:24:44 mout sshd[30529]: Did not receive identification string from 185.132.53.237 port 38280
Sep  9 13:25:00 mout sshd[30588]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.132.53.237  user=root
Sep  9 13:25:03 mout sshd[30588]: Failed password for root from 185.132.53.237 port 42012 ssh2
2020-09-09 20:08:08
164.90.208.135 attack
ET SCAN Sipvicious Scan - port: 5060 proto: sip cat: Attempted Information Leakbytes: 456
2020-09-09 20:20:37
189.45.198.214 attackspam
failed_logins
2020-09-09 19:48:35
51.75.52.127 attackbots
Port scanning [5 denied]
2020-09-09 20:13:43
45.142.120.61 attackspam
Sep  9 00:45:52 marvibiene postfix/smtpd[2152]: warning: unknown[45.142.120.61]: SASL LOGIN authentication failed: VXNlcm5hbWU6
Sep  9 01:49:15 marvibiene postfix/smtpd[5442]: warning: unknown[45.142.120.61]: SASL LOGIN authentication failed: VXNlcm5hbWU6
2020-09-09 20:12:08

Recently Reported IPs

102.220.95.192 102.220.41.195 102.220.39.170 102.220.52.115
102.220.71.209 102.220.27.65 102.220.4.33 102.220.225.146
102.220.231.249 102.220.76.96 102.220.51.161 102.220.21.174
102.220.49.194 102.220.45.170 102.220.233.140 102.220.28.182
102.220.207.189 102.220.234.105 102.220.20.211 102.220.239.221