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

Region: New Jersey

Country: United States

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

;; QUESTION SECTION:
;104.102.129.158.		IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 18 00:32:20 CST 2022
;; MSG SIZE  rcvd: 108
Host info
158.129.102.104.in-addr.arpa domain name pointer a104-102-129-158.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
158.129.102.104.in-addr.arpa	name = a104-102-129-158.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.71.223.129 attack
Invalid user langlais from 167.71.223.129 port 38482
2020-01-04 04:10:04
159.89.134.64 attack
Invalid user nasuka from 159.89.134.64 port 50182
2020-01-04 04:32:23
189.112.228.153 attackbots
Jan  3 21:44:28 main sshd[2164]: Failed password for invalid user mitchell from 189.112.228.153 port 58037 ssh2
2020-01-04 04:06:23
106.13.134.164 attackbotsspam
Invalid user dennard from 106.13.134.164 port 55072
2020-01-04 04:39:18
139.217.227.32 attackbots
Invalid user movie from 139.217.227.32 port 49246
2020-01-04 04:11:13
182.71.108.154 attackbots
Invalid user melissa from 182.71.108.154 port 34718
2020-01-04 04:08:08
185.95.186.98 attackspam
Automatic report - Port Scan Attack
2020-01-04 04:28:27
188.166.8.178 attack
ssh failed login
2020-01-04 04:07:03
138.197.176.130 attackbotsspam
Jan  3 13:29:48 ws22vmsma01 sshd[66634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.176.130
Jan  3 13:29:50 ws22vmsma01 sshd[66634]: Failed password for invalid user webadm from 138.197.176.130 port 50380 ssh2
...
2020-01-04 04:34:22
138.197.89.212 attackspam
Jan  3 15:12:17 main sshd[25310]: Failed password for invalid user oracle from 138.197.89.212 port 35452 ssh2
2020-01-04 04:11:38
180.179.120.70 attackbots
Invalid user king from 180.179.120.70 port 58035
2020-01-04 04:30:31
5.196.226.217 attackbotsspam
Unauthorized connection attempt detected from IP address 5.196.226.217 to port 22
2020-01-04 04:23:40
35.243.115.20 attack
35.243.115.20 - - [03/Jan/2020:12:59:23 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
35.243.115.20 - - [03/Jan/2020:12:59:25 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-04 04:22:28
42.119.222.206 attackbotsspam
Invalid user pi from 42.119.222.206 port 58494
2020-01-04 04:22:03
194.96.75.180 attackbots
Invalid user reng from 194.96.75.180 port 47136
2020-01-04 04:27:22

Recently Reported IPs

104.102.129.112 104.102.129.35 104.102.130.150 104.102.131.13
104.102.133.155 104.102.135.108 104.102.135.132 104.102.135.188
104.102.135.85 103.27.117.165 103.27.124.20 103.27.124.6
103.27.201.215 103.29.31.103 103.35.65.124 103.36.122.131
103.38.4.238 103.38.80.137 103.38.80.138 103.38.80.139