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-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βNSns-cloud-c2.googledomains.com2026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βNSns-cloud-c3.googledomains.com2026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βNSns-cloud-c4.googledomains.com2026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βMXshadow-relay.mxrouting.net2026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βMXshadow.mxrouting.net2026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
βA35.245.187.852026-02-15 β 2026-04-23 Β· 2 obs
β 2026-04-23 19:28:20
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com... | 10 records |
| element.how | ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com | - |
β Authoritative Response
Server:216.239.38.108
NS records: ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for element.how (unsigned zone)
β±οΈ Timing
Total: 600ms | 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-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-tld4.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
Hierarchy
element.how is parent of data.element.how and www.element.how.
IP Addresses
element.how resolves to a single IP address: 35.245.187.85.
Other host names including airwarriorcourage.com, www.spacconference.com, kimballtrombone.com, wp-outlet.com and darrensmithmd.com share IP numbers with element.how.
Name Servers
element.how is delegated 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 at least partially shares name servers with other domains, including backorderbob.com, rlebran.com, pchww.com, datience.com and alexandriakenyon.com.
Hosts with two IP numbers:
Host ns-cloud-c1.googledomains.com points to 2001:4860:4802:32::6c and 216.239.32.108
Host ns-cloud-c2.googledomains.com points to 2001:4860:4802:34::6c and 216.239.34.108
Host ns-cloud-c3.googledomains.com points to 2001:4860:4802:36::6c and 216.239.36.108
Host ns-cloud-c4.googledomains.com points to 2001:4860:4802:38::6c and 216.239.38.108
Mail Servers
element.how is handled by two mail servers: shadow-relay.mxrouting.net and shadow.mxrouting.net.
element.how shares its mail server setup with other domains, including 925films.com, ov.nu, webdesignoshawa.ca, sarahpeacock.net and digitalworldytourism.es.
The mail servers for element.how are shared with other domains, for instance thestockers.net, geekonascooter.com, harvie.us, kernswag.com and theleadingarticles.com.
Host names with a single IP:
- shadow-relay.mxrouting.net points to 168.119.148.109
- shadow.mxrouting.net points to 168.119.148.109
Host names that point to 168.119.148.109: shadow-relay.mxrouting.net and shadow.mxrouting.net