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

Region: Tamil Nadu

Country: India

Internet Service Provider: Reliance

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:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '49.32.0.0 - 49.47.255.255'

% Abuse contact for '49.32.0.0 - 49.47.255.255' is 'ip.abuse@ril.com'

inetnum:        49.32.0.0 - 49.47.255.255
netname:        RELIANCEJIO-IN
descr:          Reliance Jio Infocomm Limited
country:        IN
org:            ORG-RJIL1-AP
admin-c:        RJIL1-AP
tech-c:         RJIL1-AP
abuse-c:        AR1022-AP
status:         ALLOCATED PORTABLE
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-IN-RELIANCEJIO
mnt-routes:     MAINT-IN-RELIANCEJIO
mnt-irt:        IRT-RELIANCEJIO-IN
last-modified:  2020-08-19T13:07:30Z
source:         APNIC

irt:            IRT-RELIANCEJIO-IN
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
e-mail:         ip.abuse@ril.com
abuse-mailbox:  ip.abuse@ril.com
admin-c:        IBSP1-AP
tech-c:         IBSP1-AP
auth:           # Filtered
remarks:        ip.abuse@ril.com was validated on 2026-02-18
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2026-02-18T13:42:51Z
source:         APNIC

organisation:   ORG-RJIL1-AP
org-name:       Reliance Jio Infocomm Limited
org-type:       LIR
country:        IN
address:        Reliance Coporate IT park LTD
address:        Ghansoli NaviMumbai
phone:          +912279670000
fax-no:         +912279610099
e-mail:         ip.management@ril.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:15:41Z
source:         APNIC

role:           ABUSE RELIANCEJIOIN
country:        ZZ
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
phone:          +000000000
e-mail:         ip.abuse@ril.com
admin-c:        IBSP1-AP
tech-c:         IBSP1-AP
nic-hdl:        AR1022-AP
remarks:        Generated from irt object IRT-RELIANCEJIO-IN
remarks:        ip.abuse@ril.com was validated on 2026-02-18
abuse-mailbox:  ip.abuse@ril.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-02-18T13:43:21Z
source:         APNIC

role:           Reliance Jio Infocomm Limited
address:        Reliance JIO INFOCOMM LTD GHANSOLI INDIA
country:        IN
phone:          +91-44770000
e-mail:         ip.management@ril.com
admin-c:        RJIL1-AP
tech-c:         RJIL1-AP
nic-hdl:        RJIL1-AP
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2016-03-09T23:55:07Z
source:         APNIC

% Information related to '49.37.208.0/20AS55836'

route:          49.37.208.0/20
origin:         AS55836
descr:          Reliance Jio Infocomm Limited
                Reliance Coporate IT park LTD
                Ghansoli NaviMumbai
mnt-by:         MAINT-IN-RELIANCEJIO
last-modified:  2020-08-24T06:57:37Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.37.217.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54446
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.37.217.45.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jul 06 08:19:04 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 45.217.37.49.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 49.37.217.45.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.212 attackspam
Brute force SMTP login attempted.
...
2020-03-31 05:31:02
66.131.216.79 attackbotsspam
2020-03-30T19:29:20.573337abusebot-3.cloudsearch.cf sshd[24394]: Invalid user test from 66.131.216.79 port 43690
2020-03-30T19:29:20.580737abusebot-3.cloudsearch.cf sshd[24394]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=modemcable079.216-131-66.mc.videotron.ca
2020-03-30T19:29:20.573337abusebot-3.cloudsearch.cf sshd[24394]: Invalid user test from 66.131.216.79 port 43690
2020-03-30T19:29:22.128204abusebot-3.cloudsearch.cf sshd[24394]: Failed password for invalid user test from 66.131.216.79 port 43690 ssh2
2020-03-30T19:34:06.608637abusebot-3.cloudsearch.cf sshd[24726]: Invalid user portal from 66.131.216.79 port 47239
2020-03-30T19:34:06.616744abusebot-3.cloudsearch.cf sshd[24726]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=modemcable079.216-131-66.mc.videotron.ca
2020-03-30T19:34:06.608637abusebot-3.cloudsearch.cf sshd[24726]: Invalid user portal from 66.131.216.79 port 47239
2020-03-30T19:34:0
...
2020-03-31 05:24:42
222.187.92.71 attackbots
Brute force SMTP login attempted.
...
2020-03-31 04:59:20
222.186.180.21 attack
Brute force SMTP login attempted.
...
2020-03-31 05:16:04
222.186.175.182 attackspam
Brute force SMTP login attempted.
...
2020-03-31 05:36:47
222.186.180.19 attack
Brute force SMTP login attempted.
...
2020-03-31 05:19:38
106.75.141.202 attack
(sshd) Failed SSH login from 106.75.141.202 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 30 19:35:37 s1 sshd[30154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.141.202  user=root
Mar 30 19:35:39 s1 sshd[30154]: Failed password for root from 106.75.141.202 port 59367 ssh2
Mar 30 19:53:38 s1 sshd[30825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.141.202  user=root
Mar 30 19:53:40 s1 sshd[30825]: Failed password for root from 106.75.141.202 port 45016 ssh2
Mar 30 19:56:44 s1 sshd[30978]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.141.202  user=root
2020-03-31 05:06:05
222.188.109.227 attackspam
Brute force SMTP login attempted.
...
2020-03-31 04:58:57
185.22.142.132 attackspam
Mar 30 22:04:25 relay dovecot: imap-login: Disconnected: Inactivity \(auth failed, 1 attempts in 180 secs\): user=\, method=PLAIN, rip=185.22.142.132, lip=176.9.177.164, session=\<++596heiR1q5Fo6E\>
Mar 30 22:04:27 relay dovecot: imap-login: Disconnected: Inactivity \(auth failed, 1 attempts in 180 secs\): user=\, method=PLAIN, rip=185.22.142.132, lip=176.9.177.164, session=\
Mar 30 22:04:33 relay dovecot: imap-login: Disconnected: Inactivity \(auth failed, 1 attempts in 180 secs\): user=\, method=PLAIN, rip=185.22.142.132, lip=176.9.177.164, session=\
Mar 30 22:04:56 relay dovecot: imap-login: Disconnected: Inactivity \(auth failed, 1 attempts in 180 secs\): user=\, method=PLAIN, rip=185.22.142.132, lip=176.9.177.164, session=\
Mar 30 22:10:06 relay dovecot: imap-login: Disconnected: Inactivity \(auth failed, 1 attempts in 180
...
2020-03-31 05:43:13
188.162.194.160 attackspam
Honeypot attack, port: 445, PTR: client.yota.ru.
2020-03-31 05:27:30
200.119.210.177 attackspam
Mar 30 15:51:34 debian-2gb-nbg1-2 kernel: \[7835351.359939\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=200.119.210.177 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=41 ID=0 DF PROTO=TCP SPT=23 DPT=49769 WINDOW=5808 RES=0x00 ACK SYN URGP=0
2020-03-31 05:33:15
123.157.255.239 attack
Mar 30 15:51:34 debian-2gb-nbg1-2 kernel: \[7835351.665365\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=123.157.255.239 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=41 ID=0 DF PROTO=TCP SPT=443 DPT=62680 WINDOW=14600 RES=0x00 ACK SYN URGP=0
2020-03-31 05:32:55
106.12.68.192 attackspambots
Mar 30 19:48:30 ns382633 sshd\[31337\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.68.192  user=root
Mar 30 19:48:32 ns382633 sshd\[31337\]: Failed password for root from 106.12.68.192 port 53708 ssh2
Mar 30 20:05:59 ns382633 sshd\[2644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.68.192  user=root
Mar 30 20:06:01 ns382633 sshd\[2644\]: Failed password for root from 106.12.68.192 port 33780 ssh2
Mar 30 20:14:27 ns382633 sshd\[4324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.68.192  user=root
2020-03-31 05:33:57
222.187.238.71 attackbotsspam
Brute force SMTP login attempted.
...
2020-03-31 05:02:42
222.187.254.189 attackspam
Brute force SMTP login attempted.
...
2020-03-31 04:59:49

Recently Reported IPs

2606:4700:10::6814:9254 2606:4700:10::6814:5608 2606:4700:10::6814:8930 2606:4700:10::6814:9570
2606:4700:10::ac43:208e 2606:4700:10::ac43:2636 54.173.13.198 54.160.214.80
52.23.168.237 167.114.103.54 13.222.61.160 61.48.147.10
149.118.133.156 100.68.203.207 2606:4700:10::6816:1829 121.230.89.136
60.166.82.50 195.96.139.178 182.242.168.168 23.177.40.241