flightcontrol.dev - dns.ninja
flightcontrol.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 | ||||||
rank #727 in the tld
🔒 HSTS Preload (+subdomains)
Subdomains
app.flightcontrol.dev |
Same first word
flightcontrol.it |
flightcontrol.com.au |
flightcontrol.com |
flightcontrol.com.br |
flightcontrol.de |
flightcontrol.dev |
flightcontrol.io |
flightcontrol.info |
DNS History
10 records (10 active, 0 former)
●NSns-1096.awsdns-09.org2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●NSns-1619.awsdns-10.co.uk2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●NSns-426.awsdns-53.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●NSns-652.awsdns-17.net2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●MXalt1.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●MXalt2.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●MXalt3.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●MXalt4.aspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●MXaspmx.l.google.com2026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
●A3.33.151.562026-03-18 → 2026-07-01 · 2 obs
● 2026-07-01 09:40:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| flightcontrol.dev | ns-652.awsdns-17.net, ns-1619.awsdns-10.co.uk, ns-426.awsdns-53.com, ns-1096.awsdns-09.org | - |
✅ Authoritative Response
Server:205.251.196.72
NS records: ns-652.awsdns-17.net, ns-1619.awsdns-10.co.uk, ns-426.awsdns-53.com, ns-1096.awsdns-09.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for flightcontrol.dev (unsigned zone)
⏱️ Timing
Total: 1770ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.33.151.56 |
| NS | 4 | ns-1096.awsdns-09.org, ns-1619.awsdns-10.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 6 | ahrefs-site-verification_61c9fa57b7e4d50, clickfunnels-domain-verification=vBXAlr... |
| SOA | 1 | ns-1096.awsdns-09.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
Hierarchy
app.flightcontrol.dev is delegated beneath flightcontrol.dev.
IP Addresses
flightcontrol.dev points to a single IP number: 3.33.151.56.
Host names such as boardwalk.marketing, dinodino.net and ac965c67804bb13fe.awsglobalaccelerator.com share their IP numbers with flightcontrol.dev.
Name Servers
flightcontrol.dev has four authoritative name servers: ns-426.awsdns-53.com, ns-652.awsdns-17.net, ns-1096.awsdns-09.org and ns-1619.awsdns-10.co.uk.
There is at least partial name server overlap between flightcontrol.dev and other domains — dissidiafantasyfinals.com, svnforum.net, dcx.no and two more among them.
These name servers are routinely deployed together with the name servers ns-1715.awsdns-22.co.uk.
All four hostnames — ns-426.awsdns-53.com, ns-652.awsdns-17.net, ns-1096.awsdns-09.org and ns-1619.awsdns-10.co.uk — resolve to two IP numbers apiece: ns-426.awsdns-53.com to 205.251.193.170 and 2600:9000:5301:aa00::1; ns-652.awsdns-17.net to 205.251.194.140 and 2600:9000:5302:8c00::1; ns-1096.awsdns-09.org to 205.251.196.72 and 2600:9000:5304:4800::1; ns-1619.awsdns-10.co.uk to 205.251.198.83 and 2600:9000:5306:5300::1.
Mail Servers
Five mail servers handle flightcontrol.dev: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
flightcontrol.dev shares mail servers — at least in part — with other domains, including kmnoodle.com.tw, ns500742.ns500742.ns500731.ns500742.ns500671.ns500705.ns500704.ns500678.ns500704.ns500688.ns500678.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500754.ns500754.ns500754.ns500742.ns500754.ns500754.ns500704.ns500705.ns500704.ns500705.ns500705.ns500291.ns500678.ns500291.ns500666.ns500291.ns500131.lustychickser.com and two others.
These mail servers are frequently used alongside mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other.
Host names with two IP numbers:
aspmx.l.google.com resolves to two addresses: 142.251.167.26 and 2607:f8b0:4004:c17::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.