apidash.dev - dns.ninja
apidash.dev
dev
| 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 | ||||||
Same first word
Similar names
dhaiaps.com |
padisha.org |
ashadip.org |
adaship.com |
hapsida.com |
aphidas.com |
dhpasia.com |
padisah.pro |
phdasia.com |
padisah.org |
padashi.com |
piashad.org |
hapiads.com |
dashapi.com |
DNS History
10 records (10 active, 0 former)
●NSns-cloud-c1.googledomains.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●NSns-cloud-c2.googledomains.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●NSns-cloud-c3.googledomains.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●NSns-cloud-c4.googledomains.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●MXalt1.aspmx.l.google.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●MXalt2.aspmx.l.google.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●MXalt3.aspmx.l.google.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●MXalt4.aspmx.l.google.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●MXaspmx.l.google.com2026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
●A199.36.158.1002026-05-01 → 2026-06-18 · 2 obs
● 2026-06-18 11:53:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | 10 records |
| apidash.dev | ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.36.108
NS records: ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 718ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.36.158.100 |
| NS | 4 | ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 4 | google-site-verification=e3J2Fl_0DFHQXcZ, v=spf1 include:_spf.google.com ~all... |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
apidash.dev directs to one IP number, which is 199.36.158.100.
Among the host names that share IP numbers with apidash.dev are uniqueapplyonliness-k.web.app, case-account-help-8aec2.firebaseapp.com, advertise-meta-case-12d2c.web.app and two others.
Name Servers
The domain apidash.dev is delegated to these four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
apidash.dev has at least partial name server overlap with other domains, such as royal-industries.com, electriceelemployment.com, findlocalfirst.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
Mail for apidash.dev is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
apidash.dev shares at least some of its mail servers with other domains — for example ns500671.ns500671.ns500754.ns500671.ns500704.ns500671.ns500704.ns500678.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500731.ns500671.ns500742.ns500754.ns500742.ns500705.ns500671.ns500705.ns500704.ns500705.ns500688.ns500688.ns500704.ns500649.ns500291.ns500649.tenderladiesbz.com, ns500671.ns500754.ns500704.ns500671.ns500704.ns500671.ns500671.ns500649.lusty(0x736c7574)z.com and two more.
It is common for these mail servers to co-occur with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 142.250.101.27 and 2607:f8b0:4023:c06::1b.
alt1.aspmx.l.google.com resolves to 172.217.216.27 and 2607:f8b0:4023:2803::1a.
alt2.aspmx.l.google.com resolves to 172.253.145.26 and 2607:f8b0:4023:3003::1a.
alt3.aspmx.l.google.com resolves to 142.251.127.26 and 2a00:1450:4001:c21::1a.
alt4.aspmx.l.google.com resolves to 142.250.147.26 and 2a00:1450:4025:c01::1b.