Skip to content
https://kqed.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
2 redirect(s), 785 ms total
REVIEW
2 redirect(s), 785 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://kqed.org to https://www.kqed.org:443/
Info::
Redirect overhead: 785 ms total
Got: 785 ms

https://kqed.org

123 ms · HTTP/1.1

301

http://www.kqed.org/

39 ms · HTTP/1.1

308

https://www.kqed.org:443/

623 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kqed.org301123 msHTTP/1.1Apache
2http://www.kqed.org/30839 msHTTP/1.1
3https://www.kqed.org:443/200623 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://kqed.org to https://www.kqed.org:443/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.kqed.org/
200https://kqed.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://kqed.org/ → https://kqed.org:443/

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
262 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

262
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.244.210.32
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1040.awsdns-02.org, ns-151.awsdns-18.com, ns-2012.awsdns-59.co.uk, ns-848.awsdns-42.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 54 ms
Got: 54 ms
A35.244.210.32
AAAA—
CNAME—
NSns-1040.awsdns-02.org, ns-151.awsdns-18.com, ns-2012.awsdns-59.co.uk, ns-848.awsdns-42.net
MX
10 us-smtp-inbound-2.mimecast.com
10 us-smtp-inbound-1.mimecast.com
TXT
MS=ms61542968
YZt3i+LWohuv2skJHKV+La53GkWSvBLlBC/eozrgp4lqSB9Sd8g5FTlr3a19B9rG8GKZ+YG4RzeXHg2Q...
_9pavhq86dj9yceu3wlvsn1ryx90vw4l
apple-domain-verification=zeTbYZsPI6j5xAwq
asv=bf30a33888fb8bc8da7c5c119636d3a0
bw=nCjXO4yhV4ExGKpGOkFM6MZlyvqbUlvdrzVh5iJg0DR4
canva-site-verification=I918bwj-w6ISDPATBioXdg
duo_sso_verification=SIumb9VaS1U0P1LH0my95iM8NgNhKsP8mkLt69qBPe3RtPcVZyoHpWOkGxH...
google-site-verification=ARRxlV-zkHSjg-dBOQiUO6P9xB8Hke3TT2fp5fZ2m8Q
google-site-verification=_E_uLynFit98fEBqsfhSuKSSIoLqDrZbyZMx4glyKVU
google-site-verification=amwULeShv2ZPNAixzupicKWW1i__ZZRMfdHBWK0MDqE
google-site-verification=d9ouHmFJXuSmD-lqK-SLjzAe4w-ZFPpexoD5Iy1EtoY
intacct-esk=874E4CC23B3E4E96E053AA06A8C02971
jamf-site-verification=mNzQ_qAiSBOzOt5YY_Abig
slack-domain-verification=XJE38n28kfp0D7q1oEJ1RGPlKhg96RvY5eFvBO7P
stripe-verification=8DF6CB0C6C9B072081453DCD92FCFFB01998F95050FBE7A4F983DCC5E65E...
SPF v=spf1 include:_spf.kqed_org._d.easydmarc.pro ~all
zapier-domain-verification-challenge=173c0a10-9edc-44a6-a1f1-1fbdf626b3c1
CAALookup not available with standard resolver
Resolved in 54 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 157 URLs
PASS
robots.txt present, sitemap with 157 URLs
Info::
robots.txt is present
Got: 134 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 157 entries
Info::
Sitemap index with 157 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 134 B Sitemaps referenced 1 User-agents facebookexternalhit/1.1, Google-Extended Blocking No — crawling allowed
Sitemap: https://www.kqed.org/sitemap-index.xml

User-agent: facebookexternalhit/1.1
Allow: /
User-agent: Google-Extended
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 157 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
kqed.org — via Amazon Registrar, Inc., 32 years, 7 months old, hosted on Google Cloud
PASS
kqed.org — via Amazon Registrar, Inc., 32 years, 7 months old, hosted on Google Cloud
Info::
Domain registered until Mar 1, 2033 (6 years, 11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Amazon Registrar, Inc.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

2450 days

March 1, 2033

SSL certificate

262 days

Issued by Sectigo Limited

Domain age

32 years, 7 months

Registered February 28, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

35.244.210.32

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Amazon Registrar, Inc.
Created February 28, 1994 (32 years, 7 months ago)
Expires March 1, 2033 (6 years, 11 months)
Last Updated February 20, 2024
Name Servers ns-1040.awsdns-02.org, ns-151.awsdns-18.com, ns-2012.awsdns-59.co.uk, ns-848.awsdns-42.net
DNSSEC Not enabled
Hosting
IP Address 35.244.210.32
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 118 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
14 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
119 ms
Total Time Total request time from DNS lookup through full response.
119 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 7 ms TLS Handshake 14 ms Server Processing 67 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback