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

Internet Service Provider: unknown

Hostname: unknown

Organization: Akamai Technologies, Inc.

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Sat May 11 00:10:37 +08 2019
;; MSG SIZE  rcvd: 117

Host info
54.132.82.104.in-addr.arpa domain name pointer a104-82-132-54.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
54.132.82.104.in-addr.arpa	name = a104-82-132-54.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
106.13.10.159 attackspambots
k+ssh-bruteforce
2019-10-02 17:52:44
193.93.192.146 attack
Ein möglicherweise gefährlicher Request.Form-Wert wurde vom Client (mp$ContentZone$TxtMessage="
2019-10-02 18:06:22
40.89.159.174 attackbots
Oct  2 07:04:25 ns41 sshd[30909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.89.159.174
2019-10-02 17:45:18
23.129.64.203 attackspam
2019-10-02T07:40:56.676357abusebot.cloudsearch.cf sshd\[13419\]: Invalid user pengkelian from 23.129.64.203 port 63905
2019-10-02 17:38:53
180.250.183.154 attackspam
Oct  2 02:38:08 mail sshd\[61822\]: Invalid user postgres from 180.250.183.154
Oct  2 02:38:08 mail sshd\[61822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.183.154
...
2019-10-02 18:07:43
2.188.34.59 attack
Automatic report - Port Scan Attack
2019-10-02 18:01:58
182.61.34.79 attackbotsspam
Oct  2 06:48:58 bouncer sshd\[3745\]: Invalid user teamspeak3 from 182.61.34.79 port 39686
Oct  2 06:48:58 bouncer sshd\[3745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.34.79 
Oct  2 06:48:59 bouncer sshd\[3745\]: Failed password for invalid user teamspeak3 from 182.61.34.79 port 39686 ssh2
...
2019-10-02 17:57:19
46.161.60.15 attack
Ein möglicherweise gefährlicher Request.Form-Wert wurde vom Client (mp$ContentZone$TxtMessage="
2019-10-02 18:07:31
88.202.200.97 attackbots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/88.202.200.97/ 
 GB - 1H : (317)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : GB 
 NAME ASN : ASN56329 
 
 IP : 88.202.200.97 
 
 CIDR : 88.202.192.0/20 
 
 PREFIX COUNT : 25 
 
 UNIQUE IP COUNT : 65280 
 
 
 WYKRYTE ATAKI Z ASN56329 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-02 05:47:05 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-10-02 18:00:01
159.203.17.176 attack
Oct  2 11:46:52 MK-Soft-VM6 sshd[19955]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.17.176 
Oct  2 11:46:54 MK-Soft-VM6 sshd[19955]: Failed password for invalid user thierry1129 from 159.203.17.176 port 35042 ssh2
...
2019-10-02 18:11:44
83.171.107.216 attackbots
Oct  2 11:48:34 ns37 sshd[27713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.171.107.216
2019-10-02 18:12:22
103.17.53.148 attack
Oct  2 06:47:09 www5 sshd\[14106\]: Invalid user login from 103.17.53.148
Oct  2 06:47:09 www5 sshd\[14106\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.17.53.148
Oct  2 06:47:12 www5 sshd\[14106\]: Failed password for invalid user login from 103.17.53.148 port 40666 ssh2
...
2019-10-02 17:55:37
49.234.3.90 attackbotsspam
2019-10-02T03:00:27.705199ns525875 sshd\[2938\]: Invalid user test from 49.234.3.90 port 57392
2019-10-02T03:00:27.710924ns525875 sshd\[2938\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.3.90
2019-10-02T03:00:29.330112ns525875 sshd\[2938\]: Failed password for invalid user test from 49.234.3.90 port 57392 ssh2
2019-10-02T03:05:09.239861ns525875 sshd\[7179\]: Invalid user vampire from 49.234.3.90 port 38418
...
2019-10-02 18:10:40
119.27.170.64 attackbots
Oct  2 11:38:02 dedicated sshd[5680]: Invalid user ec2-user from 119.27.170.64 port 59666
2019-10-02 17:50:14
116.247.85.132 attackbotsspam
Oct  2 12:55:06 site3 sshd\[210401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.247.85.132  user=root
Oct  2 12:55:09 site3 sshd\[210401\]: Failed password for root from 116.247.85.132 port 53538 ssh2
Oct  2 12:55:14 site3 sshd\[210406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.247.85.132  user=root
Oct  2 12:55:16 site3 sshd\[210406\]: Failed password for root from 116.247.85.132 port 53736 ssh2
Oct  2 12:55:21 site3 sshd\[210408\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.247.85.132  user=root
...
2019-10-02 17:58:04

Recently Reported IPs

95.68.92.3 132.209.206.43 105.72.59.163 213.55.184.142
136.59.205.238 102.165.39.56 126.46.60.42 71.64.200.188
152.168.247.167 1.233.4.49 217.192.33.239 115.96.64.82
165.255.146.13 156.200.39.34 5.250.138.51 65.96.151.68
209.157.41.139 14.124.194.87 37.187.0.223 50.32.235.171