hyperpg.in - dns.ninja
hyperpg.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns1.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| NS | ns2.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns3.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns4.registry.in ⚠️ Not in parent delegation | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1781359867 | ||||||
Same first word
hyperpg.in |
DNS History
18 records (12 active, 6 former)
●NSns-1430.awsdns-50.org2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●NSns-1587.awsdns-06.co.uk2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●NSns-645.awsdns-16.net2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●NSns-67.awsdns-08.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●MXalt1.aspmx.l.google.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●MXalt2.aspmx.l.google.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●MXalt3.aspmx.l.google.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●MXalt4.aspmx.l.google.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
●MXaspmx.l.google.com2026-02-16 → 2026-06-13 · 2 obs
● 2026-06-13 14:21:22
○A13.205.231.282026-02-16 → 2026-02-19 · 4 obs
● 2026-02-19 01:16:36
○ 2026-02-26 14:40:00
○ 2026-06-13 14:21:22
●A13.207.117.1122026-06-13 → 2026-06-13 · 3 obs
● 2026-06-13 14:21:20
● 2026-06-13 14:21:22
○A13.235.253.2022026-02-26 → 2026-02-26 · 4 obs
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-06-13 14:21:22
○A15.206.218.42026-02-19 → 2026-02-26 · 5 obs
● 2026-02-19 00:44:02
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-06-13 14:21:22
○A15.206.220.1132026-02-16 → 2026-02-19 · 4 obs
● 2026-02-19 01:16:36
○ 2026-02-26 14:40:00
○ 2026-06-13 14:21:22
○A3.108.68.1252026-02-26 → 2026-02-26 · 4 obs
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-06-13 14:21:22
●A3.111.98.1272026-06-13 → 2026-06-13 · 3 obs
● 2026-06-13 14:21:20
● 2026-06-13 14:21:22
●A43.205.187.1272026-06-13 → 2026-06-13 · 3 obs
● 2026-06-13 14:21:20
● 2026-06-13 14:21:22
○A65.2.62.1182026-02-16 → 2026-02-16 · 3 obs
○ 2026-02-19 00:44:02
○ 2026-06-13 14:21:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| hyperpg.in | ns-67.awsdns-08.com, ns-645.awsdns-16.net, ns-1430.awsdns-50.org, ns-1587.awsdns-06.co.uk | - |
✅ Authoritative Response
Server:205.251.198.51
NS records: ns-67.awsdns-08.com, ns-645.awsdns-16.net, ns-1430.awsdns-50.org, ns-1587.awsdns-06.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hyperpg.in (unsigned zone)
⏱️ Timing
Total: 341ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 43.205.187.127, 3.111.98.127... |
| NS | 4 | ns-1430.awsdns-50.org, ns-1587.awsdns-06.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com include:a |
| SOA | 1 | ns-67.awsdns-08.com awsdns-hostmaster.am |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)
Analysis
IP Addresses
hyperpg.in directs to three IP numbers: 3.111.98.127, 13.207.117.112 and 43.205.187.127.
Name Servers
hyperpg.in is delegated to four name servers, ns-67.awsdns-08.com, ns-645.awsdns-16.net, ns-1430.awsdns-50.org and ns-1587.awsdns-06.co.uk.
There is at least partial name server overlap between hyperpg.in and other domains — 35.78.3.in-addr.arpa, 159.181.63.in-addr.arpa, intertel.jp and two more among them.
These name servers tend to appear in combination with the name servers ns1-24-eu-central-1.ec2-rdns.amazonaws.com, ns2-24-eu-central-1.ec2-rdns.amazonaws.com, ns3-24-eu-central-1.ec2-rdns.amazonaws.com and ns4-24-eu-central-1.ec2-rdns.amazonaws.com.
All four hostnames — ns-67.awsdns-08.com, ns-645.awsdns-16.net, ns-1430.awsdns-50.org and ns-1587.awsdns-06.co.uk — resolve to two IP numbers apiece: ns-67.awsdns-08.com to 205.251.192.67 and 2600:9000:5300:4300::1; ns-645.awsdns-16.net to 205.251.194.133 and 2600:9000:5302:8500::1; ns-1430.awsdns-50.org to 205.251.197.150 and 2600:9000:5305:9600::1; ns-1587.awsdns-06.co.uk to 205.251.198.51 and 2600:9000:5306:3300::1.
Mail Servers
Five mail servers handle hyperpg.in: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between hyperpg.in and other domains, including ns500731.ns500742.ns500731.ns500671.ns500742.ns500671.ns500671.ns500705.ns500671.ns500291.ns500688.ns500291.ns500666.ns500291.ns500131.lustychickser.com, ns500758.ns500698.ns500759.ns500758.ns500735.ns500735.ns500736.ns500698.ns500576.ns500708.ns500708.ns500576.ns500652.trackreceptor.com, ns500759.ns500759.ns500759.ns500698.ns500736.ns500735.ns500736.ns500735.ns500698.ns500698.ns500708.ns500708.ns500698.ns500698.ns500652.ns500652.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to 172.253.63.26 and 2607:f8b0:4004:c25::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.145.26 and 2607:f8b0:4023:3003::1a.
alt3.aspmx.l.google.com resolves to 172.253.135.27 and 2607:f8b0:4023:1015::1b.
alt4.aspmx.l.google.com resolves to 173.194.42.27 and 2607:f8b0:4001:c79::1b.