firebytes.in - dns.ninja
firebytes.in
| DNSSEC | ⚠️ Not signed | ||||||
| A | 168.62.237.96🇺🇸 Microsoft168.62.0.0/15 MICROSOFT | ||||||
| NS | ns1.hover.com ⭐ | ||||||
| A | 2604:4000:0:d:216:40:47:26🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns1.hover.com | ||||||
| A | 216.40.47.26🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0 | ||||||
| PTR | ns1.hover.com | ||||||
| NS | ns2.hover.com | ||||||
| A | 2604:4000:2800:d:64:99:148:13🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co. | ||||||
| PTR | ns2.hover.com | ||||||
| A | 64.98.148.13🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co. | ||||||
| PTR | ns2.hover.com | ||||||
| SOA | ns1.hover.comdnsmaster@hover.com serial=1720468956 | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in ⚠️ Not in parent delegation | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782565564 | ||||||
Same first word
DNS History
9 records (3 active, 6 former)
●NSns1.hover.com2026-03-30 → 2026-06-27 · 3 obs
● 2026-03-30 04:25:42
● 2026-06-27 13:50:54
○NSns1dhl.name.com2015-06-01 → 2017-07-05 · 4 obs
● 2017-07-05 03:55:26
○ 2026-03-30 04:25:42
○ 2026-06-27 13:50:54
●NSns2.hover.com2026-03-30 → 2026-06-27 · 3 obs
● 2026-03-30 04:25:42
● 2026-06-27 13:50:54
○NSns2nsy.name.com2015-06-01 → 2017-07-05 · 4 obs
● 2017-07-05 03:55:26
○ 2026-03-30 04:25:42
○ 2026-06-27 13:50:54
○NSns3gmt.name.com2015-06-01 → 2017-07-05 · 4 obs
● 2017-07-05 03:55:26
○ 2026-03-30 04:25:42
○ 2026-06-27 13:50:54
○NSns4sxy.name.com2015-06-01 → 2017-07-05 · 4 obs
● 2017-07-05 03:55:26
○ 2026-03-30 04:25:42
○ 2026-06-27 13:50:54
●A168.62.237.962016-09-12 → 2026-06-27 · 3 obs
● 2016-09-12 00:07:46
● 2026-06-27 13:50:54
○A75.126.101.2342016-04-04 → 2016-04-04 · 4 obs
● 2016-04-04 19:14:38
○ 2016-09-12 00:07:46
○ 2026-06-27 13:50:54
○A75.126.102.2332015-06-01 → 2015-12-28 · 4 obs
● 2015-12-28 01:13:04
○ 2016-04-04 19:14:38
○ 2026-06-27 13:50:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns01.trs-dns.net, ns10.trs-dns.org, ns1.registry.in, ns3.registry.in | 8 records |
| firebytes.in | ns2.hover.com, ns1.hover.com | - |
✅ Authoritative Response
Server:64.98.148.13
NS records: ns2.hover.com, ns1.hover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for firebytes.in (unsigned zone)
⏱️ Timing
Total: 519ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 168.62.237.96 |
| NS | 2 | ns1.hover.com, ns2.hover.com |
| SOA | 1 | ns1.hover.com dnsmaster.hover.com |
📌 Glue Records Collected
Total: 8
In-bailiwick: 4 (ns1.registry.in, ns3.registry.in, ns1.registry.in...)
Out-of-bailiwick: 4 (ns01.trs-dns.net, ns10.trs-dns.org, ns01.trs-dns.net...)
Analysis
IP Addresses
firebytes.in resolves to one IP address: 168.62.237.96.
Name Servers
firebytes.in uses two name servers for its delegation: ns1.hover.com and ns2.hover.com.
firebytes.in uses the same name servers as several other domains — among them badgerbase.com, foodstate.com, vintagecostumejewelry.com and two more.
firebytes.in shares at least some of its name servers with other domains, including walrus.ca, nbalive.gg, sysadminday.com and two others.
These name servers are frequently seen alongside the name servers ns3.hover.com.
The two host names ns1.hover.com and ns2.hover.com each have a pair of IP addresses: ns1.hover.com has 216.40.47.26 and 2604:4000:0:d:216:40:47:26, and ns2.hover.com has 64.98.148.13 and 2604:4000:2800:d:64:99:148:13.