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

;; QUESTION SECTION:
;104.125.80.81.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 12 05:19:24 CST 2022
;; MSG SIZE  rcvd: 106
Host info
81.80.125.104.in-addr.arpa domain name pointer a104-125-80-81.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
81.80.125.104.in-addr.arpa	name = a104-125-80-81.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
110.80.142.84 attackbotsspam
Jan  1 12:13:33 TORMINT sshd\[21922\]: Invalid user test from 110.80.142.84
Jan  1 12:13:33 TORMINT sshd\[21922\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.80.142.84
Jan  1 12:13:35 TORMINT sshd\[21922\]: Failed password for invalid user test from 110.80.142.84 port 36984 ssh2
...
2020-01-02 02:03:06
41.40.150.60 attackspam
Fail2Ban Ban Triggered
2020-01-02 02:06:11
178.157.219.105 attackspam
WordPress wp-login brute force :: 178.157.219.105 0.160 - [01/Jan/2020:14:49:53  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1806 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-01-02 01:51:26
178.242.24.7 attackbotsspam
Fail2Ban Ban Triggered
2020-01-02 01:48:06
63.81.87.194 attackbots
Jan  1 15:49:50  exim[12123]: [1\47] 1imfJl-00039X-Bq H=silver.jcnovel.com (silver.iposttr.com) [63.81.87.194] F= rejected after DATA: This message scored 101.5 spam points.
2020-01-02 01:45:17
118.24.149.173 attackbotsspam
Jan  1 14:49:26 IngegnereFirenze sshd[30177]: Failed password for invalid user asterisk from 118.24.149.173 port 60258 ssh2
...
2020-01-02 02:01:47
195.24.207.199 attack
Jan  1 17:06:12 raspberrypi sshd\[869\]: Invalid user arindam from 195.24.207.199Jan  1 17:06:14 raspberrypi sshd\[869\]: Failed password for invalid user arindam from 195.24.207.199 port 37754 ssh2Jan  1 17:13:22 raspberrypi sshd\[1107\]: Invalid user hsuyp from 195.24.207.199
...
2020-01-02 01:47:45
218.92.0.145 attackbotsspam
Jan  2 00:33:18 lcl-usvr-02 sshd[14925]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.145  user=root
Jan  2 00:33:19 lcl-usvr-02 sshd[14925]: Failed password for root from 218.92.0.145 port 57345 ssh2
...
2020-01-02 01:40:41
223.164.6.198 attackbotsspam
Jan  1 15:48:52 grey postfix/smtpd\[23593\]: NOQUEUE: reject: RCPT from unknown\[223.164.6.198\]: 554 5.7.1 Service unavailable\; Client host \[223.164.6.198\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[223.164.6.198\]\; from=\ to=\ proto=ESMTP helo=\<\[223.164.6.198\]\>
...
2020-01-02 02:15:08
82.146.46.189 attackspam
Jan  1 09:49:53 plusreed sshd[6422]: Invalid user ssh from 82.146.46.189
...
2020-01-02 01:50:26
188.166.117.213 attackbotsspam
$f2bV_matches
2020-01-02 02:08:29
83.212.109.91 attackspambots
Jan  1 17:36:20 v22018076622670303 sshd\[15410\]: Invalid user ryanlee from 83.212.109.91 port 38252
Jan  1 17:36:20 v22018076622670303 sshd\[15410\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.212.109.91
Jan  1 17:36:22 v22018076622670303 sshd\[15410\]: Failed password for invalid user ryanlee from 83.212.109.91 port 38252 ssh2
...
2020-01-02 01:54:37
151.80.254.74 attack
2020-01-01T14:40:33.468363abusebot-2.cloudsearch.cf sshd[25810]: Invalid user tomoko from 151.80.254.74 port 39118
2020-01-01T14:40:33.476765abusebot-2.cloudsearch.cf sshd[25810]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.254.74
2020-01-01T14:40:33.468363abusebot-2.cloudsearch.cf sshd[25810]: Invalid user tomoko from 151.80.254.74 port 39118
2020-01-01T14:40:35.839419abusebot-2.cloudsearch.cf sshd[25810]: Failed password for invalid user tomoko from 151.80.254.74 port 39118 ssh2
2020-01-01T14:49:42.505505abusebot-2.cloudsearch.cf sshd[26356]: Invalid user guest from 151.80.254.74 port 41962
2020-01-01T14:49:42.511312abusebot-2.cloudsearch.cf sshd[26356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.254.74
2020-01-01T14:49:42.505505abusebot-2.cloudsearch.cf sshd[26356]: Invalid user guest from 151.80.254.74 port 41962
2020-01-01T14:49:44.573079abusebot-2.cloudsearch.cf sshd[26356]: Fai
...
2020-01-02 01:53:19
222.186.42.4 attack
Jan  1 19:13:43 meumeu sshd[14060]: Failed password for root from 222.186.42.4 port 50370 ssh2
Jan  1 19:14:01 meumeu sshd[14060]: error: maximum authentication attempts exceeded for root from 222.186.42.4 port 50370 ssh2 [preauth]
Jan  1 19:14:07 meumeu sshd[14110]: Failed password for root from 222.186.42.4 port 45678 ssh2
...
2020-01-02 02:16:02
91.137.16.128 attack
Automated report (2020-01-01T14:49:40+00:00). Misbehaving bot detected at this address.
2020-01-02 01:56:07

Recently Reported IPs

88.12.245.170 224.151.169.24 8.107.107.20 51.77.157.202
65.2.76.107 249.114.134.100 57.3.225.248 232.19.18.90
245.163.208.63 47.234.160.252 60.48.10.38 61.98.141.232
115.114.89.79 145.108.154.102 31.93.181.93 246.237.172.21
225.201.128.244 169.198.123.109 106.103.237.40 46.92.137.112