data.element.how - dns.ninja
data.element.how
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.76.60.229🇺🇸 AS-VULTR45.76.60.0/22 Vultr Assigned Prefix | ||||||
| PTR | 45.76.60.229.vultrusercontent.com | ||||||
element.how
| DNSSEC | ⚠️ Not signed | ||||||
| A | 35.245.187.85🇺🇸 Google35.245.176.0/20 | ||||||
| NS | ns-cloud-c1.googledomains.com ⭐ | ||||||
| NS | ns-cloud-c2.googledomains.com | ||||||
| NS | ns-cloud-c3.googledomains.com | ||||||
| NS | ns-cloud-c4.googledomains.com | ||||||
| MX | shadow-relay.mxrouting.net ⭐ | ||||||
| MX | shadow.mxrouting.net(20) | ||||||
| TXT | brevo-code:d6cbbef55cd46102638f7d3ea441761e | ||||||
| SOA | ns-cloud-c1.googledomains.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
●A45.76.60.2292026-04-24 → 2026-06-28 · 2 obs
● 2026-04-24 00:02:36
● 2026-06-28 12:25:20
● 2026-06-28 12:25:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld1.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.38.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: 435ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.76.60.229 |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
data.element.how has exactly one IP address — 45.76.60.229.