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

;; QUESTION SECTION:
;48.107.52.13.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 18:21:51 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 13.52.107.48.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 13.52.107.48.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
86.61.66.59 attack
Jul 17 20:16:04 srv206 sshd[9958]: Invalid user hue from 86.61.66.59
...
2019-07-18 02:52:44
78.129.83.98 attackspambots
SASL Brute Force
2019-07-18 02:36:25
206.189.130.251 attack
2019-07-17T18:37:53.276364abusebot-3.cloudsearch.cf sshd\[13020\]: Invalid user user01 from 206.189.130.251 port 51868
2019-07-18 02:48:00
128.199.216.250 attackbots
Jul 17 23:58:36 vibhu-HP-Z238-Microtower-Workstation sshd\[4102\]: Invalid user aileen from 128.199.216.250
Jul 17 23:58:36 vibhu-HP-Z238-Microtower-Workstation sshd\[4102\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.216.250
Jul 17 23:58:38 vibhu-HP-Z238-Microtower-Workstation sshd\[4102\]: Failed password for invalid user aileen from 128.199.216.250 port 58576 ssh2
Jul 18 00:05:19 vibhu-HP-Z238-Microtower-Workstation sshd\[4387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.216.250  user=root
Jul 18 00:05:21 vibhu-HP-Z238-Microtower-Workstation sshd\[4387\]: Failed password for root from 128.199.216.250 port 57876 ssh2
...
2019-07-18 02:38:33
85.50.202.61 attack
Jul 17 20:56:54 rpi sshd[25013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.50.202.61 
Jul 17 20:56:57 rpi sshd[25013]: Failed password for invalid user webmo from 85.50.202.61 port 37934 ssh2
2019-07-18 02:59:54
148.66.135.35 attackspambots
Jul 17 20:36:24 ubuntu-2gb-nbg1-dc3-1 sshd[31550]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.35
Jul 17 20:36:26 ubuntu-2gb-nbg1-dc3-1 sshd[31550]: Failed password for invalid user gu from 148.66.135.35 port 60896 ssh2
...
2019-07-18 03:11:42
104.140.188.38 attackspam
firewall-block, port(s): 3389/tcp
2019-07-18 03:00:48
49.88.112.65 attack
2019-07-17T19:04:56.298682abusebot.cloudsearch.cf sshd\[24460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.65  user=root
2019-07-18 03:16:38
196.219.231.180 attackspambots
Multiple failed RDP login attempts
2019-07-18 02:57:54
167.71.204.13 attack
Jul 17 18:33:26 XXXXXX sshd[13682]: Invalid user admin from 167.71.204.13 port 39132
2019-07-18 03:06:32
172.104.65.226 attackspam
" "
2019-07-18 02:58:16
203.48.246.66 attackspambots
Jul 17 16:35:41 sshgateway sshd\[21444\]: Invalid user webmaster from 203.48.246.66
Jul 17 16:35:41 sshgateway sshd\[21444\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.48.246.66
Jul 17 16:35:44 sshgateway sshd\[21444\]: Failed password for invalid user webmaster from 203.48.246.66 port 50630 ssh2
2019-07-18 02:56:06
46.3.96.70 attack
17.07.2019 18:32:49 Connection to port 18523 blocked by firewall
2019-07-18 02:52:18
103.55.89.228 attackbotsspam
TCP port 23 (Telnet) attempt blocked by firewall. [2019-07-17 18:56:49]
2019-07-18 02:31:43
194.230.159.213 attack
Jul1718:02:45server4dovecot:imap-login:Disconnected:Inactivity\(authfailed\,1attemptsin179secs\):user=\\,method=PLAIN\,rip=88.149.142.194\,lip=148.251.104.70\,TLS\,session=\<9gsJleKNAqFYlY7C\>Jul1717:44:37server4dovecot:imap-login:Disconnected\(authfailed\,1attemptsin16secs\):user=\\,method=PLAIN\,rip=88.149.142.194\,lip=148.251.104.70\,TLS:Connectionclosed\,session=\Jul1717:44:37server4dovecot:imap-login:Disconnected\(authfailed\,1attemptsin14secs\):user=\\,method=PLAIN\,rip=88.149.142.194\,lip=148.251.104.70\,TLS:Connectionclosed\,session=\Jul1718:34:55server4dovecot:imap-login:Disconnected\(authfailed\,1attemptsin6secs\):user=\\,method=PLAIN\,rip=194.230.159.213\,lip=148.251.104.70\,TLS\,session=\Jul1718:02:39server4dovecot:imap-login:Disconnected:Inactivity\(authfailed\,1attemptsin179secs\):user=\\,method=PLAIN\,rip=88.149.142.194\,lip=
2019-07-18 03:21:05

Recently Reported IPs

198.68.236.218 157.155.210.136 51.67.103.106 232.148.231.43
18.70.212.88 96.224.183.244 124.58.143.77 69.20.103.169
78.38.101.206 207.4.61.5 115.146.13.117 99.82.164.94
57.252.114.58 4.199.78.16 157.73.46.170 170.203.47.115
118.164.178.101 210.229.168.157 161.237.94.110 53.253.65.60