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

;; QUESTION SECTION:
;104.12.4.16.			IN	A

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

;; Query time: 82 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 21:38:46 CST 2022
;; MSG SIZE  rcvd: 104
Host info
16.4.12.104.in-addr.arpa domain name pointer 104-12-4-16.lightspeed.sndgca.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
16.4.12.104.in-addr.arpa	name = 104-12-4-16.lightspeed.sndgca.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
154.209.253.149 attackspam
The IP has triggered Cloudflare WAF. CF-Ray: 544c6689cd0184d0 | WAF_Rule_ID: 53b8357af6d244d3a132bcf913c3a388 | WAF_Kind: firewall | CF_Action: drop | Country: HK | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: skk.moe | User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0) | CF_DC: HKG. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-15 01:49:13
198.27.80.123 attackspam
Time:     Sat Dec 14 12:21:23 2019 -0300
IP:       198.27.80.123 (CA/Canada/ns524016.ip-198-27-80.net)
Failures: 20 (WordPressBruteForcePOST)
Interval: 3600 seconds
Blocked:  Permanent Block
2019-12-15 01:30:53
103.16.223.254 attackspam
k+ssh-bruteforce
2019-12-15 01:56:26
217.114.209.240 attackbots
POST /login/  Attempting to login via port 2083.  No user agent.
2019-12-15 01:30:18
31.171.108.133 attackbots
Dec 14 20:32:31 server sshd\[21176\]: Invalid user cis from 31.171.108.133
Dec 14 20:32:31 server sshd\[21176\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.171.108.133 
Dec 14 20:32:33 server sshd\[21176\]: Failed password for invalid user cis from 31.171.108.133 port 36772 ssh2
Dec 14 20:39:28 server sshd\[22990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.171.108.133  user=root
Dec 14 20:39:31 server sshd\[22990\]: Failed password for root from 31.171.108.133 port 55884 ssh2
...
2019-12-15 01:56:52
80.82.64.214 attackspam
19/12/14@11:18:32: FAIL: IoT-SSH address from=80.82.64.214
...
2019-12-15 01:54:05
77.247.181.165 attackspambots
/.bitcoin/backup.dat
/.bitcoin/bitcoin.dat
/.bitcoin/wallet.dat
/backup.dat
/backup/backup.dat
/backup/bitcoin.dat
/backup/wallet.dat
/bitcoin.dat
2019-12-15 01:38:26
185.220.101.3 attackbotsspam
Looking for resource vulnerabilities
2019-12-15 01:33:12
49.234.134.253 attackbotsspam
Dec 14 18:47:02 MK-Soft-VM7 sshd[21917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.134.253 
Dec 14 18:47:05 MK-Soft-VM7 sshd[21917]: Failed password for invalid user mysql from 49.234.134.253 port 50784 ssh2
...
2019-12-15 01:52:00
222.186.42.4 attackspambots
Dec 14 18:51:29 vpn01 sshd[27442]: Failed password for root from 222.186.42.4 port 9184 ssh2
Dec 14 18:51:42 vpn01 sshd[27442]: error: maximum authentication attempts exceeded for root from 222.186.42.4 port 9184 ssh2 [preauth]
...
2019-12-15 01:55:34
222.186.175.154 attackbots
Dec 14 17:55:10 zeus sshd[2336]: Failed password for root from 222.186.175.154 port 48026 ssh2
Dec 14 17:55:15 zeus sshd[2336]: Failed password for root from 222.186.175.154 port 48026 ssh2
Dec 14 17:55:19 zeus sshd[2336]: Failed password for root from 222.186.175.154 port 48026 ssh2
Dec 14 17:55:23 zeus sshd[2336]: Failed password for root from 222.186.175.154 port 48026 ssh2
Dec 14 17:55:27 zeus sshd[2336]: Failed password for root from 222.186.175.154 port 48026 ssh2
2019-12-15 01:59:49
14.175.176.73 attack
Brute forcing RDP port 3389
2019-12-15 01:55:10
80.91.176.139 attack
Dec 14 06:37:35 wbs sshd\[22066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.91.176.139  user=root
Dec 14 06:37:38 wbs sshd\[22066\]: Failed password for root from 80.91.176.139 port 41179 ssh2
Dec 14 06:43:25 wbs sshd\[22717\]: Invalid user jacoby from 80.91.176.139
Dec 14 06:43:25 wbs sshd\[22717\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.91.176.139
Dec 14 06:43:27 wbs sshd\[22717\]: Failed password for invalid user jacoby from 80.91.176.139 port 46062 ssh2
2019-12-15 02:05:30
54.153.199.84 attack
RDP brute forcing (d)
2019-12-15 02:04:43
78.46.48.98 attackbots
GET /wp-admin/user/profile.php
2019-12-15 01:38:08

Recently Reported IPs

27.5.26.149 195.29.77.21 143.107.154.18 111.43.137.205
89.248.163.158 124.80.140.209 120.85.92.142 45.83.65.230
120.85.143.176 109.195.112.209 78.187.87.193 104.227.30.154
27.215.209.207 200.29.111.72 136.32.53.25 94.179.17.110
68.132.41.4 43.131.65.253 146.158.30.175 222.237.16.246