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

;; QUESTION SECTION:
;204.113.13.48.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 19 00:49:29 CST 2022
;; MSG SIZE  rcvd: 106
Host info
48.13.113.204.in-addr.arpa domain name pointer utah.gov.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
48.13.113.204.in-addr.arpa	name = utah.gov.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.16.10.158 attackspam
05/08/2020-14:15:44.428802 81.16.10.158 Protocol: 6 ET POLICY Cleartext WordPress Login
2020-05-08 20:44:57
195.53.63.194 attackspambots
Brute force SMTP login attempted.
...
2020-05-08 20:40:36
185.123.205.46 attackspambots
Automatic report - WordPress Brute Force
2020-05-08 20:19:08
177.43.79.4 attackbots
May  8 14:15:54 mail sshd\[10905\]: Invalid user nwu from 177.43.79.4
May  8 14:15:54 mail sshd\[10905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.43.79.4
May  8 14:15:56 mail sshd\[10905\]: Failed password for invalid user nwu from 177.43.79.4 port 46062 ssh2
...
2020-05-08 20:20:02
183.162.79.39 attackspambots
2020-05-08T06:22:21.605171linuxbox-skyline sshd[22045]: Invalid user px from 183.162.79.39 port 50231
...
2020-05-08 20:31:12
222.209.85.197 attackbots
May  8 14:14:25 localhost sshd\[23154\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.209.85.197  user=root
May  8 14:14:27 localhost sshd\[23154\]: Failed password for root from 222.209.85.197 port 55946 ssh2
May  8 14:15:45 localhost sshd\[23324\]: Invalid user ubuntu from 222.209.85.197
May  8 14:15:45 localhost sshd\[23324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.209.85.197
May  8 14:15:47 localhost sshd\[23324\]: Failed password for invalid user ubuntu from 222.209.85.197 port 42782 ssh2
...
2020-05-08 20:36:53
218.21.240.24 attack
(sshd) Failed SSH login from 218.21.240.24 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  8 12:07:13 amsweb01 sshd[27880]: Invalid user sysadmin from 218.21.240.24 port 52876
May  8 12:07:15 amsweb01 sshd[27880]: Failed password for invalid user sysadmin from 218.21.240.24 port 52876 ssh2
May  8 12:11:10 amsweb01 sshd[28541]: Invalid user student from 218.21.240.24 port 14429
May  8 12:11:12 amsweb01 sshd[28541]: Failed password for invalid user student from 218.21.240.24 port 14429 ssh2
May  8 12:12:35 amsweb01 sshd[28655]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.21.240.24  user=root
2020-05-08 20:02:51
118.24.71.83 attack
$f2bV_matches
2020-05-08 20:44:33
80.82.77.86 attack
Port scan(s) denied
2020-05-08 20:03:44
202.168.71.146 attackspam
2020-05-08T13:09:27.7598831240 sshd\[31825\]: Invalid user deploy from 202.168.71.146 port 56756
2020-05-08T13:09:27.7637121240 sshd\[31825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.168.71.146
2020-05-08T13:09:30.1829001240 sshd\[31825\]: Failed password for invalid user deploy from 202.168.71.146 port 56756 ssh2
...
2020-05-08 20:03:13
49.206.12.208 attack
Unauthorized connection attempt from IP address 49.206.12.208 on Port 445(SMB)
2020-05-08 20:39:52
54.37.224.163 attackbotsspam
May  8 14:11:50 electroncash sshd[33165]: Invalid user guest from 54.37.224.163 port 50288
May  8 14:11:50 electroncash sshd[33165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.224.163 
May  8 14:11:50 electroncash sshd[33165]: Invalid user guest from 54.37.224.163 port 50288
May  8 14:11:51 electroncash sshd[33165]: Failed password for invalid user guest from 54.37.224.163 port 50288 ssh2
May  8 14:15:43 electroncash sshd[34237]: Invalid user adrian from 54.37.224.163 port 59640
...
2020-05-08 20:45:14
190.143.202.194 attackspambots
Unauthorized connection attempt from IP address 190.143.202.194 on Port 445(SMB)
2020-05-08 20:35:25
103.28.52.84 attackbotsspam
May  8 17:17:52 gw1 sshd[18139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.28.52.84
May  8 17:17:54 gw1 sshd[18139]: Failed password for invalid user liuxin from 103.28.52.84 port 54184 ssh2
...
2020-05-08 20:29:43
151.101.38.214 attackspambots
05/08/2020-14:30:51.660040 151.101.38.214 Protocol: 6 SURICATA TLS invalid record/traffic
2020-05-08 20:32:31

Recently Reported IPs

204.11.98.77 204.111.6.122 204.11.98.68 204.11.98.70
204.111.112.141 204.113.4.220 204.115.119.107 204.116.183.196
204.116.182.196 204.114.10.200 204.12.107.40 204.115.226.22
204.12.118.145 204.12.13.212 204.116.47.71 204.12.14.179
204.115.119.81 204.12.13.56 204.12.195.42 204.12.211.114