hyperpg.in - dns.ninja

`hyperpg.in`

DNSSEC	⚠️ Not signed
A	3.6.237.203^{🇮🇳 Amazon3.6.0.0/15 EC2 GRU prefix}
		PTR	`ec2-3-6-237-203.ap-south-1.compute.amazonaws.com`
A	13.127.110.83^{🇮🇳 Amazon13.126.0.0/15 EC2 BOM prefix}
A	13.207.89.156^{🇺🇸 Amazon13.204.0.0/14 EC2 BOM prefix}
NS	`ns-67.awsdns-08.com` ⭐
		A	2600:9000:5300:4300::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-67.awsdns-08.com`
		A	205.251.192.67^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-67.awsdns-08.com`
NS	`ns-1430.awsdns-50.org`
		A	2600:9000:5305:9600::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1430.awsdns-50.org`
		A	205.251.197.150^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1430.awsdns-50.org`
NS	`ns-1587.awsdns-06.co.uk`
		A	2600:9000:5306:3300::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1587.awsdns-06.co.uk`
		A	205.251.198.51^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1587.awsdns-06.co.uk`
NS	`ns-645.awsdns-16.net`
		A	2600:9000:5302:8500::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-645.awsdns-16.net`
		A	205.251.194.133^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-645.awsdns-16.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:amazonses.com include:zoho.in include:...`
SOA	`ns-67.awsdns-08.com`awsdns-hostmaster@amazon.com serial=1

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.trs-dns.com` ⭐
	NS	`ns1.registry.in`
	NS	`ns2.registry.in`
	NS	`ns3.registry.in`
	NS	`ns4.registry.in`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1786270854

Same first word

hyperpg.in

DNS History

24 records (12 active, 12 former)

●NSns-1430.awsdns-50.org2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●NSns-1587.awsdns-06.co.uk2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●NSns-645.awsdns-16.net2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●NSns-67.awsdns-08.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●MXalt1.aspmx.l.google.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●MXalt2.aspmx.l.google.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●MXalt3.aspmx.l.google.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●MXalt4.aspmx.l.google.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

●MXaspmx.l.google.com2026-02-16 → 2026-08-09 · 2 obs

● 2026-02-16 13:08:08
● 2026-08-09 10:25:36

○A13.126.198.232026-07-01 → 2026-07-01 · 3 obs

○ 2026-06-13 14:21:20
● 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

●A13.127.110.832026-08-09 → 2026-08-09 · 2 obs

○ 2026-07-01 23:12:52
● 2026-08-09 10:25:36

○A13.202.8.992026-07-01 → 2026-07-01 · 3 obs

○ 2026-06-13 14:21:20
● 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

○A13.205.231.282026-02-16 → 2026-02-19 · 4 obs

● 2026-02-16 13:08:08
● 2026-02-19 01:16:36
○ 2026-02-26 14:40:00
○ 2026-08-09 10:25:36

○A13.207.117.1122026-06-13 → 2026-06-13 · 4 obs

○ 2026-02-26 14:40:00
● 2026-06-13 14:21:20
○ 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

●A13.207.89.1562026-08-09 → 2026-08-09 · 2 obs

○ 2026-07-01 23:12:52
● 2026-08-09 10:25:36

○A13.235.253.2022026-02-26 → 2026-02-26 · 4 obs

○ 2026-02-19 01:16:36
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-08-09 10:25:36

○A15.206.218.42026-02-19 → 2026-02-26 · 5 obs

○ 2026-02-16 13:08:08
● 2026-02-19 00:44:02
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-08-09 10:25:36

○A15.206.220.1132026-02-16 → 2026-02-19 · 4 obs

● 2026-02-16 13:08:08
● 2026-02-19 01:16:36
○ 2026-02-26 14:40:00
○ 2026-08-09 10:25:36

○A15.207.118.1302026-07-01 → 2026-07-01 · 3 obs

○ 2026-06-13 14:21:20
● 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

○A3.108.68.1252026-02-26 → 2026-02-26 · 4 obs

○ 2026-02-19 01:16:36
● 2026-02-26 14:40:00
○ 2026-06-13 14:21:20
○ 2026-08-09 10:25:36

○A3.111.98.1272026-06-13 → 2026-06-13 · 4 obs

○ 2026-02-26 14:40:00
● 2026-06-13 14:21:20
○ 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

●A3.6.237.2032026-08-09 → 2026-08-09 · 2 obs

○ 2026-07-01 23:12:52
● 2026-08-09 10:25:36

○A43.205.187.1272026-06-13 → 2026-06-13 · 4 obs

○ 2026-02-26 14:40:00
● 2026-06-13 14:21:20
○ 2026-07-01 23:12:52
○ 2026-08-09 10:25:36

○A65.2.62.1182026-02-16 → 2026-02-16 · 3 obs

● 2026-02-16 13:08:08
○ 2026-02-19 00:44:02
○ 2026-08-09 10:25:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns3.registry.in, ns4.registry.in, ns1.registry.in, ns2.registry.in	-
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.197.150

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: 1399ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`13.207.89.156, 13.127.110.83...`
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`

Analysis

IP Addresses

hyperpg.in directs to three IP numbers: 3.6.237.203, 13.127.110.83 and 13.207.89.156.

ec2-13-127-110-83.ap-south-1.compute.amazonaws.com is an example of another host name that shares IP numbers with hyperpg.in.

Name Servers

The NS records for hyperpg.in point 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 192.178.155.26 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.