Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2643 ms totalFIX
https://pew.org
1283 ms · HTTP/1.1
https://www.pew.org/
230 ms · HTTP/1.1
https://www.pew.org/en/
1130 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://pew.org | 301 | 1283 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
| 2 | https://www.pew.org/ | 302 | 230 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.pew.org/en/ | 200 | 1130 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BHTTP Probe TimingTotal 1095 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations77 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
- 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
ADNS Records1 A records, 604 ms lookupPASS
| A | 104.45.130.11 |
| AAAA | — |
| CNAME | — |
| NS | dns4.name-services.com, dns2.name-services.com, dns5.name-services.com, dns1.name-services.com, dns3.name-services.com |
| MX | 0 pew-org.mail.protection.outlook.com |
| TXT | SPF v=spf1 include:spf.protection.outlook.com include:cust-spf.exacttarget.com -all yahoo-verification-key=IAy8Mg+Bphl1AP7GMWVv135oQreXz5fAxJVk1deWv9Y= apple-domain-verification=ttDB0TbWvZFWAPDT google-site-verification=OvT8zfK-geEzWX5FLVesSmGAvce3KVdF6ybZkhzvEl8 MS=ms83181169 cn0vmmopisrpo4mbs8rcamcfm0 google-site-verification=8MsIRqTsvKWVRcjRQTLSpozZhIuWDTE9gxlTYxC7Ah4 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 3 URLsPASS
User-agent: Twitterbot
Disallow:
User-agent: *
Crawl-delay: 2
Disallow: /search
Disallow: /projects/pew-biomedical-scholars/directory-of-pew-scholars/search
Disallow: /projects/pew-latin-american-fellows/directory-of-latin-fellows/search
Disallow: /projects/marine-fellows/fellows-directory/search
Disallow: /projects/pew-stewart-scholars-for-cancer-research/directory-of-stewart-scholars/search
Disallow: /api/*
Disallow: /sitecore/*
Disallow: /sessioninfo.aspx
Disallow: /error/*
Sitemap: https://www.pew.org/site-map
Sitemap: https://www.pew.org/video-site-map
Disallow: /en/microsites/
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencepew.org — via eNom, LLC, 29 years, 5 months old, hosted on Microsoft AzurePASS
307 days
April 17, 2027
77 days
Issued by Let's Encrypt
29 years, 5 months
Registered April 16, 1997
Not enabled
Protects against DNS spoofing
Microsoft Azure
ASN AS8075
104.45.130.11
eNom, LLC
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