element.how - robtex.com
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-01 · 2 obs
● 2026-06-01 07:45:12
●NSns-cloud-c2.googledomains.com2026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
●NSns-cloud-c3.googledomains.com2026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
●NSns-cloud-c4.googledomains.com2026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
●MXshadow-relay.mxrouting.net2026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
●MXshadow.mxrouting.net2026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
●A35.245.187.852026-02-15 → 2026-06-01 · 2 obs
● 2026-06-01 07:45:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| element.how | ns-cloud-c4.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com | - |
✅ Authoritative Response
Server:216.239.36.108
NS records: ns-cloud-c4.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for element.how (unsigned zone)
⏱️ Timing
Total: 911ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.245.187.85 |
| NS | 4 | ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com... |
| MX | 2 | shadow-relay.mxrouting.net (pri: 20), shadow.mxrouting.net (pri: 10) |
| TXT | 1 | brevo-code:d6cbbef55cd46102638f7d3ea4417 |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Hierarchy
data.element.how and www.element.how are both subdomains of element.how.
IP Addresses
element.how resolves to one IP address: 35.245.187.85.
airwarriorcourage.com, www.spacconference.com, kimballtrombone.com and two other host names share IP numbers with element.how.
Name Servers
element.how delegates DNS authority to 4 name servers — ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
There is at least partial name server overlap between element.how and other domains — backorderbob.com, rlebran.com, pchww.com and two more among them.
All four hostnames — ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com — resolve to two IP numbers apiece: ns-cloud-c1.googledomains.com to 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com to 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com to 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com to 216.239.38.108 and 2001:4860:4802:38::6c.
Mail Servers
Mail for element.how is handled by two mail servers — shadow-relay.mxrouting.net and shadow.mxrouting.net.
element.how uses an identical mail server configuration to several other domains — among them 925films.com, ov.nu, webdesignoshawa.ca and two more.
element.how has at least partial mail server overlap with other domains such as thestockers.net, geekonascooter.com, harvie.us and two more.
shadow-relay.mxrouting.net and shadow.mxrouting.net each point to one IP address — 168.119.148.109.
The host names shadow-relay.mxrouting.net and shadow.mxrouting.net both resolve to 168.119.148.109 IP addresses.