element.how - dns.ninja
element.how
how
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Subdomains
Same first word
Similar names
DNS History
7 records (7 active, 0 former)
●NSns-cloud-c1.googledomains.com2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●NSns-cloud-c2.googledomains.com2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●NSns-cloud-c3.googledomains.com2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●NSns-cloud-c4.googledomains.com2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●MXshadow-relay.mxrouting.net2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●MXshadow.mxrouting.net2026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
●A35.245.187.852026-02-15 → 2026-06-28 · 2 obs
● 2026-06-28 14:16:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com... | 10 records |
| element.how | ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com | - |
✅ Authoritative Response
Server:216.239.36.108
NS records: ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for element.how (unsigned zone)
⏱️ Timing
Total: 558ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.245.187.85 |
| NS | 4 | ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com... |
| MX | 2 | shadow.mxrouting.net (pri: 10), shadow-relay.mxrouting.net (pri: 20) |
| TXT | 1 | brevo-code:d6cbbef55cd46102638f7d3ea4417 |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Hierarchy
data.element.how and www.element.how each fall under element.how as their parent domain.
IP Addresses
element.how resolves to just one IP address, 35.245.187.85.
Two other host names, along with airwarriorcourage.com, www.spacconference.com and kimballtrombone.com, also share IP numbers with element.how.
Name Servers
The NS records for element.how point to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
element.how has at least partial name server overlap with other domains, such as backorderbob.com, rlebran.com, pchww.com and two others.
ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com all point to exactly two IP numbers each: ns-cloud-c1.googledomains.com → 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com → 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com → 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com → 216.239.38.108 and 2001:4860:4802:38::6c.
Mail Servers
element.how is served by two mail servers, shadow-relay.mxrouting.net and shadow.mxrouting.net.
Among the domains sharing a mail server setup with element.how are 925films.com, ov.nu, jnsn.io and two others.
There is at least a partial MX overlap between element.how and other domains, including thestockers.net, geekonascooter.com, harvie.us and two others.
Both shadow-relay.mxrouting.net and shadow.mxrouting.net have a single IP address, 168.119.148.109, and share it.
Host names pointing to 168.119.148.109 IP addresses: shadow-relay.mxrouting.net and shadow.mxrouting.net.