bytephase.in - robtex.com
bytephase.in
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.comtrs-ops@tucows.com serial=1783094767 | ||||||
Subdomains
www.bytephase.in |
Same first word
bytephase.com |
bytephase.in |
Similar names
DNS History
10 records (10 active, 0 former)
●NSns-1440.awsdns-52.org2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●NSns-1685.awsdns-18.co.uk2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●NSns-503.awsdns-62.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●NSns-805.awsdns-36.net2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●MXalt1.aspmx.l.google.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●MXalt2.aspmx.l.google.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●MXalt3.aspmx.l.google.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●MXalt4.aspmx.l.google.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●MXaspmx.l.google.com2026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
●A65.2.97.122026-02-16 → 2026-07-03 · 2 obs
● 2026-07-03 16:14:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in | - |
| bytephase.in | ns-503.awsdns-62.com, ns-805.awsdns-36.net, ns-1440.awsdns-52.org, ns-1685.awsdns-18.co.uk | - |
✅ Authoritative Response
Server:205.251.198.149
NS records: ns-503.awsdns-62.com, ns-805.awsdns-36.net, ns-1440.awsdns-52.org, ns-1685.awsdns-18.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bytephase.in (unsigned zone)
⏱️ Timing
Total: 1587ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.2.97.12 |
| NS | 4 | ns-1440.awsdns-52.org, ns-1685.awsdns-18.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | google-site-verification=BPoyqy0CWmA3tGp |
| SOA | 1 | ns-503.awsdns-62.com awsdns-hostmaster.a |
Analysis
Hierarchy
www.bytephase.in is delegated beneath bytephase.in.
IP Addresses
bytephase.in points to a single IP number: 65.2.97.12.
Further host names like ec2-65-2-97-12.ap-south-1.compute.amazonaws.com and www.bytephase.in overlap in IP numbers with bytephase.in.
Name Servers
bytephase.in has four authoritative name servers: ns-503.awsdns-62.com, ns-805.awsdns-36.net, ns-1440.awsdns-52.org and ns-1685.awsdns-18.co.uk.
There is at least partial name server overlap between bytephase.in and other domains — ingage.io, glide.house, 2022u.link and two more among them.
These name servers are routinely deployed together with the name servers ns-1910.awsdns-46.co.uk.
All four hostnames — ns-503.awsdns-62.com, ns-805.awsdns-36.net, ns-1440.awsdns-52.org and ns-1685.awsdns-18.co.uk — resolve to two IP numbers apiece: ns-503.awsdns-62.com to 205.251.193.247 and 2600:9000:5301:f700::1; ns-805.awsdns-36.net to 205.251.195.37 and 2600:9000:5303:2500::1; ns-1440.awsdns-52.org to 205.251.197.160 and 2600:9000:5305:a000::1; ns-1685.awsdns-18.co.uk to 205.251.198.149 and 2600:9000:5306:9500::1.
Mail Servers
bytephase.in has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
bytephase.in shares mail servers — at least in part — with other domains, including rothemail.net, paintreatmentspecialists.com, danielkatev.com and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.