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: Frankfurt am Main

Region: Hesse

Country: Germany

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.129.7 attackbotsspam
Unauthorized connection attempt detected from IP address 104.248.129.7 to port 6000 [J]
2020-03-03 00:41:59
104.248.129.227 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-29 21:45:35
104.248.129.60 attack
This IP address was blacklisted for the following reason:  /de//typo3 @ 2019-08-02T16:07:37+02:00.
2019-08-03 03:41:56
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.248.129.119
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58668
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.248.129.119.		IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 01 15:46:44 CST 2022
;; MSG SIZE  rcvd: 108
Host info
119.129.248.104.in-addr.arpa domain name pointer linkedninja.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
119.129.248.104.in-addr.arpa	name = linkedninja.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
137.74.25.247 attackspambots
Automatic report - Banned IP Access
2019-10-31 00:43:29
140.143.98.35 attackspam
Oct 30 12:35:37 ny01 sshd[19184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.98.35
Oct 30 12:35:39 ny01 sshd[19184]: Failed password for invalid user mkdir from 140.143.98.35 port 48148 ssh2
Oct 30 12:42:42 ny01 sshd[19834]: Failed password for root from 140.143.98.35 port 57778 ssh2
2019-10-31 00:55:40
111.231.90.155 attack
2019-10-30T15:41:38.390870abusebot-7.cloudsearch.cf sshd\[15886\]: Invalid user 7ygv from 111.231.90.155 port 33688
2019-10-31 00:32:30
176.8.90.149 attack
firewall-block, port(s): 2089/tcp, 3371/tcp, 3403/tcp
2019-10-31 00:40:50
182.69.93.5 attackspambots
445/tcp
[2019-10-30]1pkt
2019-10-31 00:19:57
62.231.175.228 attackbotsspam
5555/tcp 5555/tcp 5555/tcp
[2019-10-30]3pkt
2019-10-31 00:17:09
114.225.61.177 attack
Oct 30 07:50:04 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[114.225.61.177]
Oct 30 07:50:06 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[114.225.61.177]
Oct 30 07:50:20 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[114.225.61.177]
Oct 30 07:50:22 esmtp postfix/smtpd[2814]: lost connection after AUTH from unknown[114.225.61.177]
Oct 30 07:50:26 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[114.225.61.177]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=114.225.61.177
2019-10-31 00:36:27
106.12.21.193 attackbots
$f2bV_matches
2019-10-31 00:13:27
157.230.119.200 attackbots
2019-10-30 04:11:56 server sshd[50541]: Failed password for invalid user betyortodontia from 157.230.119.200 port 52856 ssh2
2019-10-31 00:45:23
106.13.130.146 attackbotsspam
2019-10-30T16:31:37.891235abusebot-3.cloudsearch.cf sshd\[1153\]: Invalid user test from 106.13.130.146 port 46474
2019-10-31 00:46:14
49.88.112.55 attackbotsspam
Oct 30 16:25:34 debian64 sshd\[7526\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.55  user=root
Oct 30 16:25:36 debian64 sshd\[7526\]: Failed password for root from 49.88.112.55 port 37852 ssh2
Oct 30 16:25:39 debian64 sshd\[7526\]: Failed password for root from 49.88.112.55 port 37852 ssh2
...
2019-10-31 00:43:46
220.191.160.42 attackspam
Oct 30 17:44:43 tuxlinux sshd[61651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.191.160.42  user=root
Oct 30 17:44:45 tuxlinux sshd[61651]: Failed password for root from 220.191.160.42 port 36178 ssh2
Oct 30 17:44:43 tuxlinux sshd[61651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.191.160.42  user=root
Oct 30 17:44:45 tuxlinux sshd[61651]: Failed password for root from 220.191.160.42 port 36178 ssh2
Oct 30 17:58:45 tuxlinux sshd[61845]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.191.160.42  user=root
...
2019-10-31 00:59:19
186.170.28.46 attack
Oct 30 02:43:22 web1 sshd\[8419\]: Invalid user logger@123 from 186.170.28.46
Oct 30 02:43:22 web1 sshd\[8419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.170.28.46
Oct 30 02:43:24 web1 sshd\[8419\]: Failed password for invalid user logger@123 from 186.170.28.46 port 34082 ssh2
Oct 30 02:48:18 web1 sshd\[8858\]: Invalid user 1qaz12341qaz from 186.170.28.46
Oct 30 02:48:18 web1 sshd\[8858\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.170.28.46
2019-10-31 00:16:19
123.207.171.211 attack
SSH Brute-Force reported by Fail2Ban
2019-10-31 00:55:20
134.209.211.153 attackspambots
fail2ban honeypot
2019-10-31 00:31:51

Recently Reported IPs

104.248.129.110 104.248.129.125 104.248.128.22 104.248.158.247
104.248.156.67 104.248.158.29 104.248.160.121 104.248.198.148
104.248.204.178 104.248.204.176 104.248.204.193 104.248.204.182
104.248.204.196 104.248.204.198 104.248.204.200 104.248.204.202
104.248.22.240 104.248.231.109 104.248.231.242 104.248.231.55