Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations312 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 84 ms lookupPASS
| A | 52.72.103.22, 34.194.143.45 |
| AAAA | — |
| CNAME | — |
| NS | ns-1643.awsdns-13.co.uk, ns-1486.awsdns-57.org, ns-689.awsdns-22.net, ns-380.awsdns-47.com |
| MX | 10 us-smtp-inbound-1.mimecast.com 10 us-smtp-inbound-2.mimecast.com |
| TXT | sophos-domain-verification=9b7065e18d586044f4f38452ac079e79bcadc41b2ff619e7b127e... 1password-site-verification=JOZOWIACJJEJTMXH5RWUXYDZBE SPF v=spf1 ip4:54.240.0.0/18 ip4:62.13.128.0/24 ip4:62.13.129.128/25 ip4:62.13.136.0... _oswq1rbknajgtqx6o35wv5pdmpbxb7w apple-domain-verification=ug7H5hlBfLwCrpT3 google-site-verification=-oXissHsEv2QBVm6AWS3CQKnP0o-W8uW1L3MXoLlksg airtable-verification=8f953d6c02a0989c9b60868a73e04103 canva-site-verification=uT2yLQklyt-NI7kG1-Shxw sp4n41djzsnx0mwnk8vqmwqhpmqd2h5t |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 914 ms totalPASS
https://wnyc.org
391 ms · HTTP/1.1
https://www.wnyc.org/
524 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wnyc.org | 301 | 391 ms | HTTP/1.1 | nginx |
| 2 | https://www.wnyc.org/ | 200 | 524 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 8 URLsPASS
User-agent: *
Disallow: /admin/
Disallow: /api/
Disallow: /atomfeeds/
Disallow: /audio/xspf/
Disallow: /email_change/
Disallow: /feeds/
Disallow: /grappelli/
Disallow: /i/
Disallow: /media/
Disallow: /music/playlists/wqxr/
Disallow: /player/
Disallow: /shows/takeaway-pm/
Disallow: /tags/
Sitemap: https://www.wnyc.org/sitemap.xml
- https://www.wnyc.org/sitemap-articlechan...
- https://www.wnyc.org/sitemap-episode.xml
- https://www.wnyc.org/sitemap-show.xml
- https://www.wnyc.org/sitemap-series.xml
- https://www.wnyc.org/sitemap-pages.xml
- https://www.wnyc.org/sitemap-article.xml
- https://www.wnyc.org/sitemap-segment.xml
- https://www.wnyc.org/sitemap-event.xml
A+Domain Intelligencewnyc.org — via Amazon Registrar, Inc., 30 years, 9 months old, hosted on AWSPASS
195 days
December 28, 2026
312 days
Issued by Amazon
30 years, 9 months
Registered December 29, 1995
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
34.194.143.45
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice