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: India

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

;; QUESTION SECTION:
;13.204.125.106.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 13:20:58 CST 2025
;; MSG SIZE  rcvd: 107
Host info
106.125.204.13.in-addr.arpa domain name pointer ec2-13-204-125-106.ap-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
106.125.204.13.in-addr.arpa	name = ec2-13-204-125-106.ap-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.74.7.251 attackbots
badbot
2019-11-24 03:24:16
114.105.173.132 attackbotsspam
badbot
2019-11-24 03:20:39
111.68.46.68 attackbotsspam
Nov 23 15:21:29 vpn01 sshd[28959]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68
Nov 23 15:21:31 vpn01 sshd[28959]: Failed password for invalid user jira from 111.68.46.68 port 37228 ssh2
...
2019-11-24 03:26:11
188.218.225.242 attackspambots
Unauthorised access (Nov 23) SRC=188.218.225.242 LEN=44 TOS=0x10 PREC=0x40 TTL=242 ID=15438 TCP DPT=1433 WINDOW=1024 SYN 
Unauthorised access (Nov 17) SRC=188.218.225.242 LEN=44 TOS=0x10 PREC=0x40 TTL=242 ID=19656 TCP DPT=445 WINDOW=1024 SYN
2019-11-24 03:03:34
122.155.174.34 attack
Nov 23 13:28:19 firewall sshd[22087]: Invalid user ttttttt from 122.155.174.34
Nov 23 13:28:21 firewall sshd[22087]: Failed password for invalid user ttttttt from 122.155.174.34 port 60260 ssh2
Nov 23 13:32:38 firewall sshd[22445]: Invalid user sairra from 122.155.174.34
...
2019-11-24 03:28:08
36.57.40.159 attackspam
badbot
2019-11-24 02:58:27
103.42.57.177 attackbotsspam
[Aegis] @ 2019-11-23 14:22:04  0000 -> Common web attack.
2019-11-24 03:09:52
213.241.46.78 attack
2019-11-23T16:03:59.886810shield sshd\[2811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=kominywulkan.pl  user=root
2019-11-23T16:04:01.765735shield sshd\[2811\]: Failed password for root from 213.241.46.78 port 52099 ssh2
2019-11-23T16:07:53.746638shield sshd\[3697\]: Invalid user home from 213.241.46.78 port 41834
2019-11-23T16:07:53.751023shield sshd\[3697\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=kominywulkan.pl
2019-11-23T16:07:56.087685shield sshd\[3697\]: Failed password for invalid user home from 213.241.46.78 port 41834 ssh2
2019-11-24 03:31:28
123.20.227.162 attackspam
2019-11-23T14:22:21.862616abusebot-6.cloudsearch.cf sshd\[12079\]: Invalid user admin from 123.20.227.162 port 47426
2019-11-24 02:55:07
51.83.138.91 attackbotsspam
51.83.138.91 was recorded 21 times by 16 hosts attempting to connect to the following ports: 33891,33890,33389,3391,33892,33896,3399,23389,13389,33899,63389,3390. Incident counter (4h, 24h, all-time): 21, 87, 4492
2019-11-24 03:07:30
138.68.52.53 attackspambots
138.68.52.53 - - \[23/Nov/2019:19:01:03 +0000\] "POST /wp-login.php HTTP/1.1" 200 4358 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
138.68.52.53 - - \[23/Nov/2019:19:01:09 +0000\] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2019-11-24 03:32:53
36.92.1.31 attackbots
fail2ban honeypot
2019-11-24 02:57:53
182.61.26.165 attackbots
Nov 23 17:21:48 microserver sshd[51169]: Invalid user ident from 182.61.26.165 port 45738
Nov 23 17:21:48 microserver sshd[51169]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.26.165
Nov 23 17:21:50 microserver sshd[51169]: Failed password for invalid user ident from 182.61.26.165 port 45738 ssh2
Nov 23 17:27:44 microserver sshd[51859]: Invalid user sidharth from 182.61.26.165 port 52070
Nov 23 17:27:44 microserver sshd[51859]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.26.165
Nov 23 17:39:21 microserver sshd[53230]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.26.165  user=root
Nov 23 17:39:22 microserver sshd[53230]: Failed password for root from 182.61.26.165 port 36488 ssh2
Nov 23 17:45:27 microserver sshd[54337]: Invalid user nfs from 182.61.26.165 port 42836
Nov 23 17:45:27 microserver sshd[54337]: pam_unix(sshd:auth): authentication failure; logname= ui
2019-11-24 03:12:01
119.250.215.85 attackbots
badbot
2019-11-24 03:12:54
49.85.238.84 attackspambots
Nov 23 23:21:39 mx1 postfix/smtpd\[9802\]: warning: unknown\[49.85.238.84\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:22:06 mx1 postfix/smtpd\[9816\]: warning: unknown\[49.85.238.84\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:22:17 mx1 postfix/smtpd\[9802\]: warning: unknown\[49.85.238.84\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-24 02:57:37

Recently Reported IPs

225.42.172.141 28.223.11.193 235.241.157.70 173.236.68.31
248.204.103.209 38.26.73.153 221.252.213.14 199.223.251.240
205.127.17.84 104.120.80.30 207.192.166.99 68.45.19.68
161.206.4.31 32.46.142.202 237.149.29.10 160.3.202.88
70.80.161.148 90.191.254.50 242.133.36.58 242.220.229.93