embarkahead.com - dns.ninja
embarkahead.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.amgen.com ⚠️ Not in zone NS records | ||||||
| A | 138.133.52.91🇺🇸 SWITCH_AMGEN138.133.52.0/24 Switch Communications Customer Route | ||||||
| PTR | ns1.amgen.com | ||||||
| NS | ns2.amgen.com ⚠️ Not in zone NS records | ||||||
| A | 138.133.61.100🇺🇸 SWITCH_AMGEN138.133.61.0/24 | ||||||
| PTR | ns2.amgen.com | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786198214 | ||||||
Same first word
embarkahead.com |
DNS History
2 records (2 active, 0 former)
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net... | - |
| embarkahead.com | ns1.amgen.com, ns2.amgen.com | 2 records |
✅ Authoritative Response
Server:138.133.52.91
NS records: ns1.amgen.com, ns2.amgen.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for embarkahead.com (unsigned zone)
⏱️ Timing
Total: 3221ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.amgen.com, ns2.amgen.com)
Analysis
Name Servers
embarkahead.com is delegated to two name servers: ns1.amgen.com and ns2.amgen.com.
embarkahead.com shares its name server setup with other domains, including sofibafusp.us, neupogen.com.pr, gcsf.ca and two others.
The name servers of embarkahead.com overlap at least partially with those of other domains — among them lumykras.in, pavblu.es, stomatitis.net and two more.
These name servers commonly appear alongside the name servers ns3.amgen.com and ns0-can.amgen.com.
Both ns1.amgen.com and ns2.amgen.com have a single IP address each — ns1.amgen.com resolves to 138.133.52.91 while ns2.amgen.com resolves to 138.133.61.100.