City: Delhi
Region: Delhi
Country: India
Internet Service Provider: AirTel
Hostname: unknown
Organization: unknown
Usage Type: unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '125.16.0.0 - 125.23.255.255'
% Abuse contact for '125.16.0.0 - 125.23.255.255' is 'dsltac2north.unoc@airtel.com'
inetnum: 125.16.0.0 - 125.23.255.255
netname: BHARTI-IN
descr: BHARTI INFOTEL LTD.
descr: ISP Division , Long Distance Group - Telesonic
descr: 234 , Okhala Phase III
descr: NEW DELHI
descr: INDIA
country: IN
org: ORG-BAL1-AP
admin-c: NA40-AP
tech-c: NA40-AP
abuse-c: AB914-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-BBIL
mnt-routes: MAINT-IN-BBIL
mnt-irt: IRT-BHARTI-TELEMEDIA-IN
last-modified: 2020-05-16T21:36:43Z
source: APNIC
irt: IRT-BHARTI-TELEMEDIA-IN
address: Bharti Airtel Ltd.
e-mail: shankar.B@airtel.com
abuse-mailbox: dsltac2north.unoc@airtel.com
admin-c: NS282-AP
tech-c: NS282-AP
auth: # Filtered
remarks: dsltac2north.unoc@airtel.com was validated on 2025-12-04
remarks: shankar.b@airtel.com was validated on 2026-02-03
mnt-by: MAINT-IN-TELEMEDIA
last-modified: 2026-02-03T23:14:59Z
source: APNIC
organisation: ORG-BAL1-AP
org-name: Bharti Airtel Limited
org-type: LIR
country: IN
address: Transport Network Group
address: 234, Okhla Phase III
phone: +911244282398
e-mail: apnic@airtel.com
mnt-ref: APNIC-HM
mnt-by: APNIC-HM
last-modified: 2023-09-05T02:14:45Z
source: APNIC
role: ABUSE BHARTITELEMEDIAIN
country: ZZ
address: Bharti Airtel Ltd.
phone: +000000000
e-mail: shankar.B@airtel.com
admin-c: NS282-AP
tech-c: NS282-AP
nic-hdl: AB914-AP
remarks: Generated from irt object IRT-BHARTI-TELEMEDIA-IN
remarks: dsltac2north.unoc@airtel.com was validated on 2025-12-04
remarks: shankar.b@airtel.com was validated on 2026-02-03
abuse-mailbox: dsltac2north.unoc@airtel.com
mnt-by: APNIC-ABUSE
last-modified: 2026-02-03T23:15:15Z
source: APNIC
person: Network Administrator
nic-hdl: NA40-AP
e-mail: noc-dataprov@airtel.com
address: Bharti Airtel Ltd.
address: ISP Division - Transport Network Group
address: Plot no.16 , Udyog Vihar , Phase -IV , Gurgaon - 122015 , Haryana , INDIA
address: Phase III, New Delhi-110020, INDIA
phone: +91-0124 4282528
fax-no: +91-124-4244017
country: IN
mnt-by: MAINT-IN-BBIL
last-modified: 2026-03-19T10:53:18Z
source: APNIC
% Information related to '125.17.121.0/24AS9498'
route: 125.17.121.0/24
descr: BHARTI-IN
descr: Bharti Tele-Ventures Limited
descr: Class A ISP in INDIA .
descr: 234 , OKHLA PHASE III ,
descr: NEW DELHI
descr: INDIA
country: IN
origin: AS9498
mnt-by: MAINT-IN-BBIL
last-modified: 2008-09-04T07:54:37Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.36-SNAPSHOT (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.17.121.250
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10666
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;125.17.121.250. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026032201 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 23 07:19:45 CST 2026
;; MSG SIZE rcvd: 107250.121.17.125.in-addr.arpa domain name pointer aes-static-250.121.17.125.airtel.in.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
250.121.17.125.in-addr.arpa name = aes-static-250.121.17.125.airtel.in.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 189.113.128.247 | attackspambots | Triggered by Fail2Ban at Vostok web server |
2019-07-10 02:11:54 |
| 165.227.122.7 | attackbotsspam | Jul 9 21:26:26 vibhu-HP-Z238-Microtower-Workstation sshd\[13686\]: Invalid user sg from 165.227.122.7 Jul 9 21:26:26 vibhu-HP-Z238-Microtower-Workstation sshd\[13686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.122.7 Jul 9 21:26:27 vibhu-HP-Z238-Microtower-Workstation sshd\[13686\]: Failed password for invalid user sg from 165.227.122.7 port 60912 ssh2 Jul 9 21:28:55 vibhu-HP-Z238-Microtower-Workstation sshd\[13762\]: Invalid user rajeev from 165.227.122.7 Jul 9 21:28:55 vibhu-HP-Z238-Microtower-Workstation sshd\[13762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.122.7 ... |
2019-07-10 02:04:12 |
| 222.87.147.62 | attack | Jul 9 18:55:25 vps647732 sshd[6324]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.87.147.62 Jul 9 18:55:28 vps647732 sshd[6324]: Failed password for invalid user james from 222.87.147.62 port 50104 ssh2 ... |
2019-07-10 02:18:10 |
| 137.59.162.169 | attack | Jul 9 18:44:31 vserver sshd\[1189\]: Invalid user red from 137.59.162.169Jul 9 18:44:33 vserver sshd\[1189\]: Failed password for invalid user red from 137.59.162.169 port 42468 ssh2Jul 9 18:49:04 vserver sshd\[1237\]: Invalid user dev from 137.59.162.169Jul 9 18:49:06 vserver sshd\[1237\]: Failed password for invalid user dev from 137.59.162.169 port 57967 ssh2 ... |
2019-07-10 01:40:55 |
| 54.37.66.73 | attack | 2019-07-09T19:32:03.3062921240 sshd\[31592\]: Invalid user administrator from 54.37.66.73 port 57029 2019-07-09T19:32:03.3105741240 sshd\[31592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.66.73 2019-07-09T19:32:04.7661901240 sshd\[31592\]: Failed password for invalid user administrator from 54.37.66.73 port 57029 ssh2 ... |
2019-07-10 02:17:33 |
| 42.99.180.167 | attack | Jul 9 15:52:37 h2177944 sshd\[7458\]: Invalid user usr01 from 42.99.180.167 port 42995 Jul 9 15:52:37 h2177944 sshd\[7458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.99.180.167 Jul 9 15:52:39 h2177944 sshd\[7458\]: Failed password for invalid user usr01 from 42.99.180.167 port 42995 ssh2 Jul 9 15:56:26 h2177944 sshd\[7501\]: Invalid user oracle from 42.99.180.167 port 33431 ... |
2019-07-10 01:46:52 |
| 3.210.199.77 | attackbots | Jul 9 13:38:31 TCP Attack: SRC=3.210.199.77 DST=[Masked] LEN=250 TOS=0x00 PREC=0x00 TTL=235 DF PROTO=TCP SPT=60396 DPT=80 WINDOW=913 RES=0x00 ACK PSH URGP=0 |
2019-07-10 01:19:12 |
| 106.13.98.202 | attackbots | Jul 9 15:34:17 meumeu sshd[15672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.202 Jul 9 15:34:19 meumeu sshd[15672]: Failed password for invalid user habib from 106.13.98.202 port 54330 ssh2 Jul 9 15:36:24 meumeu sshd[16074]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.98.202 ... |
2019-07-10 01:51:47 |
| 138.197.221.114 | attackbotsspam | Invalid user karim from 138.197.221.114 port 60972 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.221.114 Failed password for invalid user karim from 138.197.221.114 port 60972 ssh2 Invalid user sk from 138.197.221.114 port 40736 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.221.114 |
2019-07-10 02:05:11 |
| 88.174.4.30 | attackspam | SSH authentication failure x 6 reported by Fail2Ban ... |
2019-07-10 01:18:19 |
| 103.9.124.29 | attackbots | " " |
2019-07-10 02:12:22 |
| 185.220.101.27 | attackbotsspam | Automatic report - Web App Attack |
2019-07-10 02:12:40 |
| 167.99.10.90 | attackbotsspam | port 23 attempt blocked |
2019-07-10 01:33:34 |
| 202.137.10.186 | attackspambots | Jul 9 15:34:39 cp sshd[12565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.137.10.186 Jul 9 15:34:41 cp sshd[12565]: Failed password for invalid user oracle from 202.137.10.186 port 37380 ssh2 Jul 9 15:37:57 cp sshd[14452]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.137.10.186 |
2019-07-10 01:25:42 |
| 130.61.83.71 | attackspambots | Jul 9 14:10:20 *** sshd[32552]: Invalid user kk from 130.61.83.71 |
2019-07-10 01:27:53 |