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

;; QUESTION SECTION:
;104.126.116.73.			IN	A

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 06 16:03:28 CST 2022
;; MSG SIZE  rcvd: 107
Host info
73.116.126.104.in-addr.arpa domain name pointer a104-126-116-73.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
73.116.126.104.in-addr.arpa	name = a104-126-116-73.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
213.247.116.88 attack
firewall-block, port(s): 9200/tcp
2019-11-01 17:31:56
210.152.127.66 attackspam
WordPress wp-login brute force :: 210.152.127.66 0.252 - [01/Nov/2019:03:51:12  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1472 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2019-11-01 16:58:08
113.53.210.136 attackspam
Nov  1 03:38:34 sanyalnet-cloud-vps2 sshd[29025]: Connection from 113.53.210.136 port 53610 on 45.62.253.138 port 22
Nov  1 03:38:34 sanyalnet-cloud-vps2 sshd[29025]: Did not receive identification string from 113.53.210.136 port 53610
Nov  1 03:38:37 sanyalnet-cloud-vps2 sshd[29026]: Connection from 113.53.210.136 port 53632 on 45.62.253.138 port 22
Nov  1 03:38:45 sanyalnet-cloud-vps2 sshd[29026]: Address 113.53.210.136 maps to node-3ns.pool-113-53.dynamic.totinternet.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov  1 03:38:45 sanyalnet-cloud-vps2 sshd[29026]: Invalid user Adminixxxr from 113.53.210.136 port 53632
Nov  1 03:38:45 sanyalnet-cloud-vps2 sshd[29026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.53.210.136
Nov  1 03:38:47 sanyalnet-cloud-vps2 sshd[29026]: Failed password for invalid user Adminixxxr from 113.53.210.136 port 53632 ssh2
Nov  1 03:38:47 sanyalnet-cloud-vps2 sshd[290........
-------------------------------
2019-11-01 17:30:30
223.78.135.244 attackspambots
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-01 17:22:57
167.99.83.237 attackspam
Invalid user io from 167.99.83.237 port 59888
2019-11-01 17:19:16
189.59.179.60 attackbots
Honeypot attack, port: 23, PTR: 189.59.179.60.dynamic.adsl.gvt.net.br.
2019-11-01 16:58:29
124.235.147.150 attackspam
Automatic report - Banned IP Access
2019-11-01 17:22:05
195.201.92.169 attackspam
Nov  1 05:12:46 dedicated sshd[28402]: Failed password for root from 195.201.92.169 port 38836 ssh2
Nov  1 05:12:44 dedicated sshd[28398]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.201.92.169  user=root
Nov  1 05:12:46 dedicated sshd[28398]: Failed password for root from 195.201.92.169 port 38820 ssh2
Nov  1 05:12:44 dedicated sshd[28422]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.201.92.169  user=root
Nov  1 05:12:46 dedicated sshd[28422]: Failed password for root from 195.201.92.169 port 38900 ssh2
2019-11-01 17:05:35
94.130.133.93 attack
Nov  1 04:31:04 xxxxxxx sshd[26229]: Did not receive identification string from 94.130.133.93 port 32886
Nov  1 04:31:04 xxxxxxx sshd[26231]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26243]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26241]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26234]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26248]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26265]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26254]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers
Nov  1 04:31:05 xxxxxxx sshd[26239]: User r.r from 94.130.133.93 not allowed because not listed in AllowUsers........
-------------------------------
2019-11-01 16:51:52
171.97.122.6 attack
Honeypot attack, port: 23, PTR: ppp-171-97-122-6.revip8.asianet.co.th.
2019-11-01 17:17:25
94.177.173.58 attackbotsspam
2019-11-01T05:59:48.182644hub.schaetter.us sshd\[11903\]: Invalid user osmc from 94.177.173.58 port 59462
2019-11-01T05:59:48.195359hub.schaetter.us sshd\[11903\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.173.58
2019-11-01T05:59:50.034108hub.schaetter.us sshd\[11903\]: Failed password for invalid user osmc from 94.177.173.58 port 59462 ssh2
2019-11-01T06:03:18.819008hub.schaetter.us sshd\[11931\]: Invalid user Otto from 94.177.173.58 port 40414
2019-11-01T06:03:18.836842hub.schaetter.us sshd\[11931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.173.58
...
2019-11-01 17:28:42
181.230.131.66 attackbotsspam
Nov  1 05:03:42 srv01 sshd[12827]: Invalid user 0 from 181.230.131.66
Nov  1 05:03:42 srv01 sshd[12827]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.230.131.66
Nov  1 05:03:42 srv01 sshd[12827]: Invalid user 0 from 181.230.131.66
Nov  1 05:03:44 srv01 sshd[12827]: Failed password for invalid user 0 from 181.230.131.66 port 40814 ssh2
Nov  1 05:08:13 srv01 sshd[13061]: Invalid user zxcvbn from 181.230.131.66
...
2019-11-01 17:20:20
138.201.222.216 attackbots
Nov  1 04:35:32 vps5 sshd[825]: Did not receive identification string from 138.201.222.216
Nov  1 04:35:32 vps5 sshd[826]: Did not receive identification string from 138.201.222.216
Nov  1 04:35:35 vps5 sshd[840]: Failed password for r.r from 138.201.222.216 port 45972 ssh2
Nov  1 04:35:35 vps5 sshd[829]: Failed password for r.r from 138.201.222.216 port 45950 ssh2
Nov  1 04:35:35 vps5 sshd[841]: Failed password for r.r from 138.201.222.216 port 45978 ssh2
Nov  1 04:35:35 vps5 sshd[852]: Failed password for r.r from 138.201.222.216 port 46012 ssh2
Nov  1 04:35:35 vps5 sshd[901]: Failed password for r.r from 138.201.222.216 port 35040 ssh2
Nov  1 04:35:35 vps5 sshd[830]: Failed password for r.r from 138.201.222.216 port 45952 ssh2
Nov  1 04:35:35 vps5 sshd[872]: Failed password for r.r from 138.201.222.216 port 34570 ssh2
Nov  1 04
.... truncated .... 

Nov  1 04:35:32 vps5 sshd[825]: Did not receive identification string from 138.201.222.216
Nov  1 04:35:32 vps5 sshd[82........
-------------------------------
2019-11-01 17:07:22
112.192.197.120 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-01 17:09:35
45.136.110.47 attackspam
Nov  1 09:59:24 mc1 kernel: \[3885081.417212\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=59475 PROTO=TCP SPT=54723 DPT=8111 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  1 10:06:16 mc1 kernel: \[3885492.933503\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=2646 PROTO=TCP SPT=54723 DPT=7863 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  1 10:09:08 mc1 kernel: \[3885664.760890\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=16931 PROTO=TCP SPT=54723 DPT=8299 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-01 17:24:57

Recently Reported IPs

104.107.8.100 104.107.40.77 104.107.35.128 104.126.116.97
104.107.9.63 104.126.116.185 104.126.181.195 104.126.116.202
104.127.167.235 104.126.118.216 104.126.119.96 117.20.53.188
104.127.170.193 104.127.161.131 104.127.19.51 117.20.53.192
104.143.94.246 104.144.109.28 104.144.103.56 104.143.112.87