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:
IP Type Details Datetime
104.248.214.153 attack
Dec 17 00:47:48 tuxlinux sshd[48318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.214.153  user=root
Dec 17 00:47:50 tuxlinux sshd[48318]: Failed password for root from 104.248.214.153 port 34088 ssh2
Dec 17 00:47:48 tuxlinux sshd[48318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.214.153  user=root
Dec 17 00:47:50 tuxlinux sshd[48318]: Failed password for root from 104.248.214.153 port 34088 ssh2
Dec 17 00:55:35 tuxlinux sshd[48425]: Invalid user 99to from 104.248.214.153 port 48812
Dec 17 00:55:35 tuxlinux sshd[48425]: Invalid user 99to from 104.248.214.153 port 48812
Dec 17 00:55:35 tuxlinux sshd[48425]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.214.153 
...
2019-12-17 08:20:58
104.248.214.153 attack
$f2bV_matches
2019-12-17 03:06:43
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.248.214.13
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10572
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.248.214.13.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 20:26:29 CST 2022
;; MSG SIZE  rcvd: 107
Host info
13.214.248.104.in-addr.arpa domain name pointer podiato.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
13.214.248.104.in-addr.arpa	name = podiato.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
182.171.245.130 attack
Oct  7 12:38:28 thevastnessof sshd[16344]: Failed password for root from 182.171.245.130 port 63161 ssh2
...
2019-10-07 20:58:56
78.129.240.214 attack
Automated report (2019-10-07T11:47:29+00:00). Probe detected.
2019-10-07 20:55:08
1.179.185.50 attackspambots
Oct  7 14:44:13 dedicated sshd[24157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50  user=root
Oct  7 14:44:16 dedicated sshd[24157]: Failed password for root from 1.179.185.50 port 35732 ssh2
2019-10-07 20:50:14
94.125.61.251 attack
Port scan
2019-10-07 20:17:36
157.52.229.199 attack
Oct  7 13:26:01 mxgate1 postfix/postscreen[15229]: CONNECT from [157.52.229.199]:38416 to [176.31.12.44]:25
Oct  7 13:26:01 mxgate1 postfix/dnsblog[15806]: addr 157.52.229.199 listed by domain zen.spamhaus.org as 127.0.0.3
Oct  7 13:26:01 mxgate1 postfix/dnsblog[15808]: addr 157.52.229.199 listed by domain bl.spamcop.net as 127.0.0.2
Oct  7 13:26:07 mxgate1 postfix/postscreen[15229]: DNSBL rank 3 for [157.52.229.199]:38416
Oct x@x
Oct  7 13:26:07 mxgate1 postfix/postscreen[15229]: DISCONNECT [157.52.229.199]:38416


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=157.52.229.199
2019-10-07 20:51:09
222.186.169.194 attackbots
SSH Brute Force, server-1 sshd[31159]: Failed password for root from 222.186.169.194 port 30902 ssh2
2019-10-07 20:57:03
89.236.246.70 attack
Automatic report - Port Scan Attack
2019-10-07 20:23:15
216.144.254.102 attackbotsspam
07.10.2019 11:52:47 Connection to port 5060 blocked by firewall
2019-10-07 20:43:14
193.31.210.45 attack
" "
2019-10-07 20:18:00
171.224.19.255 attackbots
19/10/7@07:48:19: FAIL: IoT-Telnet address from=171.224.19.255
...
2019-10-07 20:20:53
188.213.174.36 attackbots
2019-10-07T12:18:38.169111shield sshd\[23265\]: Invalid user Philippe2017 from 188.213.174.36 port 50870
2019-10-07T12:18:38.175162shield sshd\[23265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.213.174.36
2019-10-07T12:18:40.400967shield sshd\[23265\]: Failed password for invalid user Philippe2017 from 188.213.174.36 port 50870 ssh2
2019-10-07T12:23:08.725873shield sshd\[23617\]: Invalid user Adolph2017 from 188.213.174.36 port 35162
2019-10-07T12:23:08.731438shield sshd\[23617\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.213.174.36
2019-10-07 20:26:54
220.119.203.83 attackbotsspam
Fail2Ban - FTP Abuse Attempt
2019-10-07 20:51:28
70.71.148.228 attackspam
2019-10-07T12:19:26.723499abusebot.cloudsearch.cf sshd\[5278\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=s01063c37866eee85.vs.shawcable.net  user=root
2019-10-07 20:45:52
45.55.182.232 attackspam
Oct  7 14:51:19 ns381471 sshd[17885]: Failed password for root from 45.55.182.232 port 52464 ssh2
Oct  7 14:54:56 ns381471 sshd[18009]: Failed password for root from 45.55.182.232 port 35920 ssh2
2019-10-07 20:59:59
177.72.13.124 attackspam
Looking for resource vulnerabilities
2019-10-07 20:46:38

Recently Reported IPs

104.248.211.184 104.248.212.12 104.248.214.145 104.248.211.30
104.248.211.44 104.248.210.191 104.248.214.132 104.248.211.34
104.248.213.33 104.248.214.155 101.109.63.51 104.248.214.194
104.248.215.253 104.248.216.26 104.248.215.169 104.248.214.169
104.248.217.40 104.248.216.204 104.248.219.167 104.248.219.65