optimizely.how - dns.ninja
optimizely.how
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-1038.awsdns-01.org ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5304:e00::1🇺🇸 Amazon2600:9000:5304::/48 - CloudFront | ||||||
| PTR | ns-1038.awsdns-01.org | ||||||
| A | 205.251.196.14🇺🇸 Amazon205.251.196.0/24 prefix | ||||||
| PTR | ns-1038.awsdns-01.org | ||||||
| NS | ns-1830.awsdns-36.co.uk ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5307:2600::1🇺🇸 Amazon2600:9000:5307::/48 - CloudFront | ||||||
| PTR | ns-1830.awsdns-36.co.uk | ||||||
| A | 205.251.199.38🇺🇸 Amazon205.251.199.0/24 prefix | ||||||
| PTR | ns-1830.awsdns-36.co.uk | ||||||
| NS | ns-217.awsdns-27.com ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5300:d900::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront | ||||||
| PTR | ns-217.awsdns-27.com | ||||||
| A | 205.251.192.217🇺🇸 Amazon205.251.192.0/24 prefix | ||||||
| PTR | ns-217.awsdns-27.com | ||||||
| NS | ns-652.awsdns-17.net ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5302:8c00::1🇺🇸 Amazon2600:9000:5302::/48 - CloudFront | ||||||
| PTR | ns-652.awsdns-17.net | ||||||
| A | 205.251.194.140🇺🇸 Amazon205.251.194.0/24 prefix | ||||||
| PTR | ns-652.awsdns-17.net | ||||||
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 | ||||||
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NSns-1038.awsdns-01.org2017-07-21 → 2026-06-08 · 3 obs
● 2017-07-21 13:55:40
● 2026-06-08 17:57:06
●NSns-1830.awsdns-36.co.uk2017-07-21 → 2026-06-08 · 3 obs
● 2017-07-21 13:55:40
● 2026-06-08 17:57:06
●NSns-217.awsdns-27.com2017-07-21 → 2026-06-08 · 3 obs
● 2017-07-21 13:55:40
● 2026-06-08 17:57:06
●NSns-652.awsdns-17.net2017-07-21 → 2026-06-08 · 3 obs
● 2017-07-21 13:55:40
● 2026-06-08 17:57:06
○NSns1.p24.dynect.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-07-21 13:55:40
○ 2026-06-08 17:57:06
○NSns2.p24.dynect.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-07-21 13:55:40
○ 2026-06-08 17:57:06
○NSns3.p24.dynect.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-07-21 13:55:40
○ 2026-06-08 17:57:06
○NSns4.p24.dynect.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-07-21 13:55:40
○ 2026-06-08 17:57:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com... | 10 records |
| optimizely.how | ns-652.awsdns-17.net, ns-217.awsdns-27.com, ns-1830.awsdns-36.co.uk, ns-1038.awsdns-01.org | - |
✅ Authoritative Response
Server:205.251.196.14
NS records: ns-652.awsdns-17.net, ns-217.awsdns-27.com, ns-1830.awsdns-36.co.uk, ns-1038.awsdns-01.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for optimizely.how (unsigned zone)
⏱️ Timing
Total: 1283ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
optimizely.how is served by 4 authoritative name servers: ns-217.awsdns-27.com, ns-652.awsdns-17.net, ns-1038.awsdns-01.org and ns-1830.awsdns-36.co.uk.
optimizely.how has at least partial name server overlap with other domains, such as arg.am, kyokuto.co.jp, tribunsolowiki.com and two others.
ns-217.awsdns-27.com, ns-652.awsdns-17.net, ns-1038.awsdns-01.org and ns-1830.awsdns-36.co.uk all point to exactly two IP numbers each: ns-217.awsdns-27.com → 205.251.192.217 and 2600:9000:5300:d900::1; ns-652.awsdns-17.net → 205.251.194.140 and 2600:9000:5302:8c00::1; ns-1038.awsdns-01.org → 205.251.196.14 and 2600:9000:5304:e00::1; ns-1830.awsdns-36.co.uk → 205.251.199.38 and 2600:9000:5307:2600::1.