node-zero.in - dns.ninja
node-zero.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=1790154055 | ||||||
Same first word
node-zero.link |
node-zero.us |
node-zero.xyz |
node-zero.io |
node-zero.org |
node-zero.fr |
node-zero.in |
node-zero.net |
node-zero.workers.dev |
node-zero.at |
Similar names
Previous names
Next names
DNS History
9 records (8 active, 1 former)
●NSns33.domaincontrol.com2026-09-16 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●NSns34.domaincontrol.com2026-09-16 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●MXalt1.aspmx.l.google.com2026-09-21 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●MXalt2.aspmx.l.google.com2026-09-21 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●MXalt3.aspmx.l.google.com2026-09-21 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●MXalt4.aspmx.l.google.com2026-09-21 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
●MXaspmx.l.google.com2026-09-21 → 2026-09-23 · 2 obs
● 2026-09-23 09:32:46
○A13.248.243.52026-09-16 → 2026-09-16 · 3 obs
○ 2026-09-21 13:31:26
○ 2026-09-23 09:32:46
●A216.198.79.12026-09-21 → 2026-09-23 · 3 obs
● 2026-09-21 13:31:26
● 2026-09-23 09:32:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in | 8 records |
| node-zero.in | ns33.domaincontrol.com, ns34.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.106.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for node-zero.in (unsigned zone)
⏱️ Timing
Total: 594ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.198.79.1 |
| NS | 2 | ns34.domaincontrol.com, ns33.domaincontrol.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | v=spf1 include:_spf.google.com include:d, google-site-verification=7iD7qsZvGW7zfFG |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (ns1.registry.in, ns1.registry.in, ns2.registry.in...)
Analysis
IP Addresses
node-zero.in resolves to one IP address: 216.198.79.1.
bolsasdasi.com.br, keystonedigi.com, mehditools.com and two other host names share IP numbers with node-zero.in.
Name Servers
node-zero.in uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.
node-zero.in uses the same name servers as several other domains — among them wpllp.ca, okemo.ski, boiler-mate.co.uk and two more.
The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
node-zero.in has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
node-zero.in has at least partial mail server overlap with other domains such as soleildorevoyage.com, leachsp.com, royaltycarpetcleaning-llc.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c19::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.