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 of America (the)

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

;; QUESTION SECTION:
;104.125.144.112.		IN	A

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

;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 03 15:07:52 CST 2025
;; MSG SIZE  rcvd: 108
Host info
112.144.125.104.in-addr.arpa domain name pointer a104-125-144-112.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
112.144.125.104.in-addr.arpa	name = a104-125-144-112.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
161.22.63.231 attack
Automatic report - Port Scan Attack
2019-08-01 08:49:02
91.204.252.130 attack
[portscan] Port scan
2019-08-01 08:41:25
46.105.127.6 attackspam
SSH Brute-Force reported by Fail2Ban
2019-08-01 08:51:22
66.165.213.100 attack
Invalid user ryan from 66.165.213.100 port 34376
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.165.213.100
Failed password for invalid user ryan from 66.165.213.100 port 34376 ssh2
Invalid user deepti from 66.165.213.100 port 60740
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.165.213.100
2019-08-01 09:02:43
36.111.131.2 attackbots
Jul 31 14:40:20 localhost kernel: [15842613.494963] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=36.111.131.2 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=233 ID=19395 PROTO=TCP SPT=57634 DPT=445 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 31 14:40:20 localhost kernel: [15842613.494990] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=36.111.131.2 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=233 ID=19395 PROTO=TCP SPT=57634 DPT=445 SEQ=1915103744 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 31 14:40:20 localhost kernel: [15842613.503522] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=36.111.131.2 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=234 ID=19395 PROTO=TCP SPT=57634 DPT=445 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 31 14:40:20 localhost kernel: [15842613.504410] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=36.111.131.2 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x
2019-08-01 09:12:10
27.16.218.47 attackspam
Caught in portsentry honeypot
2019-08-01 08:58:12
14.161.16.62 attackspam
Aug  1 01:56:13 docs sshd\[54661\]: Invalid user november from 14.161.16.62Aug  1 01:56:15 docs sshd\[54661\]: Failed password for invalid user november from 14.161.16.62 port 44092 ssh2Aug  1 02:01:13 docs sshd\[54784\]: Invalid user carlos1 from 14.161.16.62Aug  1 02:01:14 docs sshd\[54784\]: Failed password for invalid user carlos1 from 14.161.16.62 port 38670 ssh2Aug  1 02:06:06 docs sshd\[54895\]: Invalid user agung from 14.161.16.62Aug  1 02:06:08 docs sshd\[54895\]: Failed password for invalid user agung from 14.161.16.62 port 33332 ssh2
...
2019-08-01 08:41:43
106.52.29.40 attackbots
Automatic report - Banned IP Access
2019-08-01 08:24:45
188.128.39.132 attackbots
Invalid user presto from 188.128.39.132 port 56182
2019-08-01 08:52:40
185.220.101.25 attack
SSH bruteforce
2019-08-01 08:33:56
203.205.53.157 attackbotsspam
Trying ports that it shouldn't be.
2019-08-01 09:06:44
24.35.80.137 attackspambots
Jul 31 23:15:39 MK-Soft-VM4 sshd\[25880\]: Invalid user gwool from 24.35.80.137 port 43958
Jul 31 23:15:39 MK-Soft-VM4 sshd\[25880\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=24.35.80.137
Jul 31 23:15:42 MK-Soft-VM4 sshd\[25880\]: Failed password for invalid user gwool from 24.35.80.137 port 43958 ssh2
...
2019-08-01 08:54:20
189.45.37.254 attackbotsspam
Jun 13 10:25:19 ubuntu sshd[3102]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.45.37.254
Jun 13 10:25:21 ubuntu sshd[3102]: Failed password for invalid user qn from 189.45.37.254 port 50844 ssh2
Jun 13 10:28:58 ubuntu sshd[3184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.45.37.254
Jun 13 10:29:00 ubuntu sshd[3184]: Failed password for invalid user edu from 189.45.37.254 port 33665 ssh2
2019-08-01 08:46:10
35.225.88.208 attack
B: /wp-login.php attack
2019-08-01 09:05:49
61.219.171.213 attack
Aug  1 00:19:37 server01 sshd\[16533\]: Invalid user samba from 61.219.171.213
Aug  1 00:19:37 server01 sshd\[16533\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.219.171.213
Aug  1 00:19:39 server01 sshd\[16533\]: Failed password for invalid user samba from 61.219.171.213 port 58874 ssh2
...
2019-08-01 08:46:42

Recently Reported IPs

244.228.150.28 47.227.88.101 86.121.61.155 64.189.184.188
27.112.51.208 81.244.123.189 178.60.62.116 255.191.189.227
165.14.86.28 136.162.206.77 33.75.250.177 53.174.11.72
109.113.143.229 198.160.56.146 35.179.62.237 120.232.8.154
47.21.189.33 164.221.22.75 75.236.144.47 104.105.122.137