radiusmanagement.in - robtex.com
radiusmanagement.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1774501860 | ||||||
Same first word
radiusmanagement.in |
DNS History
20 records (8 active, 12 former)
○NSdns1.bigrock.in2020-03-29 → 2020-03-29 · 3 obs
● 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○NSdns2.bigrock.in2020-03-29 → 2020-03-29 · 3 obs
● 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○NSdns3.bigrock.in2020-03-29 → 2020-03-29 · 3 obs
● 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○NSdns4.bigrock.in2020-03-29 → 2020-03-29 · 3 obs
● 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
●NSns03.domaincontrol.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 05:26:00
●NSns04.domaincontrol.com2026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 05:26:00
○NSns1.md-in-8.webhostbox.net2015-08-07 → 2016-07-22 · 4 obs
● 2016-07-22 23:38:18
○ 2017-04-02 19:49:10
○ 2026-03-26 05:26:00
○NSns1.technofirm.net2017-04-02 → 2017-04-02 · 4 obs
● 2017-04-02 19:49:10
○ 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○NSns2.md-in-8.webhostbox.net2015-08-07 → 2016-07-22 · 4 obs
● 2016-07-22 23:38:18
○ 2017-04-02 19:49:10
○ 2026-03-26 05:26:00
○NSns2.technofirm.net2017-04-02 → 2017-04-02 · 4 obs
● 2017-04-02 19:49:10
○ 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
●MXalt1.aspmx.l.google.com2020-03-29 → 2026-03-26 · 3 obs
● 2020-03-29 19:48:26
● 2026-03-26 05:26:00
●MXalt2.aspmx.l.google.com2020-03-29 → 2026-03-26 · 3 obs
● 2020-03-29 19:48:26
● 2026-03-26 05:26:00
●MXalt3.aspmx.l.google.com2020-03-29 → 2026-03-26 · 3 obs
● 2020-03-29 19:48:26
● 2026-03-26 05:26:00
●MXalt4.aspmx.l.google.com2020-03-29 → 2026-03-26 · 3 obs
● 2020-03-29 19:48:26
● 2026-03-26 05:26:00
●MXaspmx.l.google.com2020-03-29 → 2026-03-26 · 3 obs
● 2020-03-29 19:48:26
● 2026-03-26 05:26:00
○MXradiusmanagement.in2015-08-07 → 2017-04-02 · 4 obs
● 2017-04-02 19:49:10
○ 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○A103.21.59.1662015-08-07 → 2016-07-22 · 4 obs
● 2016-07-22 23:38:18
○ 2017-04-02 19:49:10
○ 2026-03-26 05:26:00
○A103.21.59.272017-04-02 → 2017-04-02 · 4 obs
● 2017-04-02 19:49:10
○ 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
○A139.59.34.1942020-03-29 → 2020-03-29 · 3 obs
● 2020-03-29 19:48:26
○ 2026-03-26 05:26:00
●A64.227.138.1492026-03-26 → 2026-03-26 · 2 obs
● 2026-03-26 05:26:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| radiusmanagement.in | ns03.domaincontrol.com, ns04.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.101.2
NS records: ns03.domaincontrol.com, ns04.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for radiusmanagement.in (unsigned zone)
⏱️ Timing
Total: 298ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.227.138.149 |
| NS | 2 | ns03.domaincontrol.com, ns04.domaincontrol.com |
| MX | 5 | alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | pom09refnqtgrcjj1e739he9u7, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns03.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
radiusmanagement.in maps to IP address 64.227.138.149.
Name Servers
Two name servers ns03.domaincontrol.com and ns04.domaincontrol.com are delegated to radiusmanagement.in.
radiusmanagement.in uses the same name server configuration as other domains, such as bonperk.com, mypetornament.com, wizardballs.org, bagcabin.com and cozypainter.com.
Host names with two IPs:
ns03.domaincontrol.com points to 2603:5:2150::2 and 97.74.101.2.
ns04.domaincontrol.com points to 2603:5:2250::2 and 173.201.69.2.
Mail Servers
radiusmanagement.in is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
radiusmanagement.in shares mail servers with other domains at least in part, for instance ns500758.ns500758.ns500758.ns500758.ns500758.ns500698.ns500735.ns500698.ns500735.ns500735.ns500698.ns500576.ns500686.ns500576.ns500576.trackreceptor.com, ns500794.ns500841.ns500794.ns500795.ns500821.ns500821.ns500821.ns500795.ns500795.ns500821.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500754.ns500754.ns500671.ns500704.ns500705.ns500704.ns500678.ns500671.ns500671.ns500649.ns500666.ns500291.ns500131.lustychickser.com, ns500724.ns500724.ns500599.ns500737.ns500583.ns500583.ns500697.ns500682.ns500583.yummyflingsfinder.com and ns500742.ns500731.ns500671.ns500671.ns500754.ns500754.ns500742.ns500742.ns500705.ns500704.ns500688.ns500649.ns500671.ns500153.tenderladiesbz.com.
These mail servers are commonly used together with aspmx2.googlemail.com and aspmx3.googlemail.com.
Two IPs per host name:
aspmx.l.google.com points to: 2607:f8b0:4023:c0b::1a and 74.125.137.26
alt1.aspmx.l.google.com points to: 2800:3f0:4003:c0f::1a and 108.177.123.27
alt2.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1a and 172.253.135.27
alt3.aspmx.l.google.com points to: 2a00:1450:4009:c0f::1b and 192.178.223.26
alt4.aspmx.l.google.com points to: 2a00:1450:4025:c01::1a and 142.250.147.26
Pattern: left IDs ascend by 9 (12, 21, 30, 39, 48); each pair of targets ascend by 9 (15/18, 24/27, 33/36, 42/45, 51/54)