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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Sat May 11 09:45:51 +08 2019
;; MSG SIZE  rcvd: 118

Host info
Host 158.109.66.102.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

** server can't find 158.109.66.102.in-addr.arpa: NXDOMAIN

Related IP info:
Related comments:
IP Type Details Datetime
111.19.162.80 attack
Jan  3 14:50:14 plex sshd[6210]: Invalid user atscale from 111.19.162.80 port 56686
2020-01-03 22:42:04
82.248.118.142 attackbotsspam
Unauthorized connection attempt detected from IP address 82.248.118.142 to port 22
2020-01-03 22:10:33
91.243.191.180 attackbots
Attempt to hack HitBTC account
2020-01-03 22:36:31
51.77.192.7 attackspambots
Jan  3 14:06:21 debian-2gb-nbg1-2 kernel: \[316108.216891\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.77.192.7 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=23506 PROTO=TCP SPT=32767 DPT=8545 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-03 22:46:30
61.222.56.80 attack
"Fail2Ban detected SSH brute force attempt"
2020-01-03 22:49:52
3.81.9.20 attack
ssh port 22
2020-01-03 22:51:55
103.36.84.180 attackbots
Jan  3 15:37:08 legacy sshd[23821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.36.84.180
Jan  3 15:37:10 legacy sshd[23821]: Failed password for invalid user kaz from 103.36.84.180 port 34774 ssh2
Jan  3 15:41:01 legacy sshd[24066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.36.84.180
...
2020-01-03 22:42:20
184.22.96.190 attackbots
Lines containing failures of 184.22.96.190
Dec 31 16:52:32 HOSTNAME sshd[14550]: Address 184.22.96.190 maps to 184-22-96-0.24.nat.tlxxxxxxxb-cgn02.myaisfibre.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 31 16:52:32 HOSTNAME sshd[14550]: Invalid user msfadmin from 184.22.96.190 port 59793
Dec 31 16:52:32 HOSTNAME sshd[14550]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.22.96.190
Dec 31 16:52:33 HOSTNAME sshd[14550]: Failed password for invalid user msfadmin from 184.22.96.190 port 59793 ssh2
Dec 31 16:52:33 HOSTNAME sshd[14550]: Connection closed by 184.22.96.190 port 59793 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=184.22.96.190
2020-01-03 22:11:21
193.32.163.9 attackbots
Port scan: Attack repeated for 24 hours
2020-01-03 22:23:09
134.175.154.22 attackspam
Jan  3 15:54:07 master sshd[5881]: Failed password for invalid user zo from 134.175.154.22 port 41150 ssh2
2020-01-03 22:23:24
3.136.6.36 attackbotsspam
Jan  3 14:13:46 kmh-sql-001-nbg01 sshd[6512]: Invalid user hduser from 3.136.6.36 port 37908
Jan  3 14:13:46 kmh-sql-001-nbg01 sshd[6512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.136.6.36
Jan  3 14:13:48 kmh-sql-001-nbg01 sshd[6512]: Failed password for invalid user hduser from 3.136.6.36 port 37908 ssh2
Jan  3 14:13:49 kmh-sql-001-nbg01 sshd[6512]: Received disconnect from 3.136.6.36 port 37908:11: Normal Shutdown, Thank you for playing [preauth]
Jan  3 14:13:49 kmh-sql-001-nbg01 sshd[6512]: Disconnected from 3.136.6.36 port 37908 [preauth]
Jan  3 14:15:26 kmh-sql-001-nbg01 sshd[6790]: Invalid user libuuid from 3.136.6.36 port 57908
Jan  3 14:15:26 kmh-sql-001-nbg01 sshd[6790]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.136.6.36


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=3.136.6.36
2020-01-03 22:12:17
45.95.32.115 attack
postfix
2020-01-03 22:42:38
94.23.50.194 attackbotsspam
2020-01-03T14:40:02.342243hz01.yumiweb.com sshd\[26208\]: Invalid user tomcat from 94.23.50.194 port 55336
2020-01-03T14:41:59.980070hz01.yumiweb.com sshd\[26218\]: Invalid user ftpuser from 94.23.50.194 port 37101
2020-01-03T14:44:04.560405hz01.yumiweb.com sshd\[26220\]: Invalid user user01 from 94.23.50.194 port 47098
...
2020-01-03 22:37:27
128.199.249.213 attack
fail2ban honeypot
2020-01-03 22:30:55
123.54.227.51 attackspambots
Jan  3 14:07:03 vpn01 sshd[29309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.54.227.51
Jan  3 14:07:05 vpn01 sshd[29309]: Failed password for invalid user ftp from 123.54.227.51 port 33284 ssh2
...
2020-01-03 22:15:51

Recently Reported IPs

35.124.232.49 78.189.200.210 190.189.183.2 219.17.23.128
20.123.141.142 9.218.53.241 5.26.109.56 109.200.159.186
177.125.62.26 40.78.133.79 84.47.160.114 177.19.238.91
83.17.35.186 92.52.206.167 173.162.229.10 45.40.201.73
63.125.10.149 5.175.2.28 48.87.7.151 176.122.56.100