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: Korea (the Republic of)

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

;; QUESTION SECTION:
;119.208.204.253.		IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 12:48:50 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 253.204.208.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 253.204.208.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.185.85.194 attackspam
DATE:2019-07-01 00:51:29, IP:85.185.85.194, PORT:ssh brute force auth on SSH service (patata)
2019-07-01 10:01:56
42.236.101.194 attack
Scanning unused Default website or suspicious access to valid sites from IP marked as abusive
2019-07-01 10:24:29
128.199.240.120 attackbots
Jun 24 23:37:28 dns4 sshd[25792]: Invalid user lydie from 128.199.240.120
Jun 24 23:37:28 dns4 sshd[25792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.240.120 
Jun 24 23:37:31 dns4 sshd[25792]: Failed password for invalid user lydie from 128.199.240.120 port 41702 ssh2
Jun 24 23:37:31 dns4 sshd[25793]: Received disconnect from 128.199.240.120: 11: Bye Bye
Jun 24 23:40:57 dns4 sshd[25863]: Invalid user suman from 128.199.240.120
Jun 24 23:40:57 dns4 sshd[25863]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.240.120 
Jun 24 23:40:59 dns4 sshd[25863]: Failed password for invalid user suman from 128.199.240.120 port 50508 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=128.199.240.120
2019-07-01 10:13:08
218.201.14.134 attackspam
Brute force attack stopped by firewall
2019-07-01 09:52:12
125.124.30.186 attackspam
Jul  1 00:58:42 MK-Soft-VM4 sshd\[27347\]: Invalid user test from 125.124.30.186 port 57884
Jul  1 00:58:42 MK-Soft-VM4 sshd\[27347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.124.30.186
Jul  1 00:58:43 MK-Soft-VM4 sshd\[27347\]: Failed password for invalid user test from 125.124.30.186 port 57884 ssh2
...
2019-07-01 10:14:08
139.59.91.139 attackspambots
ssh failed login
2019-07-01 09:43:42
182.75.201.82 attackbots
Jul  1 04:06:22 SilenceServices sshd[31627]: Failed password for root from 182.75.201.82 port 36789 ssh2
Jul  1 04:08:03 SilenceServices sshd[32666]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.201.82
Jul  1 04:08:05 SilenceServices sshd[32666]: Failed password for invalid user minecraft from 182.75.201.82 port 53376 ssh2
2019-07-01 10:13:49
123.234.215.242 attack
'IP reached maximum auth failures for a one day block'
2019-07-01 09:57:30
186.215.199.69 attackspam
Brute force attack stopped by firewall
2019-07-01 09:41:05
158.69.222.2 attack
Jul  1 00:51:01 dedicated sshd[306]: Invalid user cr from 158.69.222.2 port 46993
Jul  1 00:51:02 dedicated sshd[306]: Failed password for invalid user cr from 158.69.222.2 port 46993 ssh2
Jul  1 00:51:01 dedicated sshd[306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.222.2
Jul  1 00:51:01 dedicated sshd[306]: Invalid user cr from 158.69.222.2 port 46993
Jul  1 00:51:02 dedicated sshd[306]: Failed password for invalid user cr from 158.69.222.2 port 46993 ssh2
2019-07-01 10:19:10
40.78.155.194 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-07-01 10:08:28
141.98.80.31 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-07-01 09:53:09
134.209.247.249 attackspam
Jul  1 00:49:42 localhost sshd\[19433\]: Invalid user kn from 134.209.247.249
Jul  1 00:49:42 localhost sshd\[19433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.247.249
Jul  1 00:49:45 localhost sshd\[19433\]: Failed password for invalid user kn from 134.209.247.249 port 41970 ssh2
Jul  1 00:51:10 localhost sshd\[19589\]: Invalid user bouncer from 134.209.247.249
Jul  1 00:51:10 localhost sshd\[19589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.247.249
...
2019-07-01 10:15:20
138.197.165.64 attackbotsspam
138.197.165.64 - - - [30/Jun/2019:22:51:06 +0000] "GET /wp-login.php HTTP/1.1" 404 162 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "-" "-"
2019-07-01 10:17:34
58.213.46.110 attack
Brute force attack stopped by firewall
2019-07-01 09:53:53

Recently Reported IPs

151.205.48.85 55.116.70.123 53.213.78.107 45.77.130.245
79.88.108.136 54.108.237.35 38.27.205.178 246.60.139.32
155.197.71.178 184.148.199.167 131.205.8.204 186.196.25.107
244.74.129.23 207.96.33.233 30.91.174.70 188.31.136.255
117.147.148.45 166.222.194.115 151.126.177.136 200.125.223.104