Skip to content
https://pewtrusts.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1252 ms total
FIX
3 redirect(s), 1252 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.pew.org/
Warning::
Redirect overhead: 1252 ms total
Got: 1252 ms
Info::
Cross-domain redirect detected

https://pewtrusts.org

395 ms · HTTP/1.1

301

https://www.pewtrusts.org/

130 ms · HTTP/1.1

301

https://www.pew.org/

248 ms · HTTP/1.1

302

https://www.pew.org/en/

479 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pewtrusts.org301395 msHTTP/1.1Microsoft-IIS/10.0
2https://www.pewtrusts.org/301130 msHTTP/1.1cloudflare
3https://www.pew.org/302248 msHTTP/1.1cloudflare
4https://www.pew.org/en/200479 msHTTP/1.1cloudflare

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

If permanent, use 301 instead.

Why this matters

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

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

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

Certificate validity

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

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
A+
DNS Records
1 A records, 154 ms lookup
PASS
1 A records, 154 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.45.130.11
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: pdns68.ultradns.co.uk, pdns68.ultradns.biz, pdns68.ultradns.net, pdns68.ultradns.com, pdns68.ultradns.org, pdns68.ultradns.info
Info::
1 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: 154 ms
Got: 154 ms
A104.45.130.11
AAAA
CNAME
NSpdns68.ultradns.co.uk, pdns68.ultradns.biz, pdns68.ultradns.net, pdns68.ultradns.com, pdns68.ultradns.org, pdns68.ultradns.info
MX
0 pewtrusts-org.mail.protection.outlook.com
TXT
atlassian-domain-verification=qOz679TjDG1e0pAfLrLtO41yqqrtdm52jm5tai43qfuDCf90yR...
MS=ms96766438
asv=17b97bd51dd6d8a1da9c76b3b7e2de91
tbce4h4igtlnjfojge0cmirnnb
MS=ms54729871
docusign=8f7243db-097e-4387-a8e1-766ce89b5d97
teamviewer-sso-verification=9f0665d783ab4d3cb0a29a5185440d66
HCkpYfj3JtKMnMO/zoESt1oqirCOj0ez8OoTNfvIjngczWADWT8AJDiDP0IIIJnMCjAxQvB8EAUUS7Jk...
ZOOM_verify_UteTLyfJZ7CtX5bvIiqTeI
workbrew-domain-verification-9s134b=Pnr3M2zGxjEut5KAJYE9Vdhcs
SPF v=spf1 include:_netblock.pewtrusts.org include:_EngagingNetworks.pewtrusts.org i...
docusign=3236b4c4-b08b-4f10-917c-1a14faa459bf
jamf-site-verification=3pfDcWku18HVh6v0hf0Xog
google-site-verification=gtLyYeX4HfCFY3vTHGh-UrfCZ9c5030PiM_baXxJcbs
vje6jsd2m0aem71h2v7daaftr3
yahoo-verification-key=ztb6Lqh1jHYmkdhd6lpDi+bokLQsyfoO6wLT6L3iE4M=
7rpohFubBIBT9TPjxZAuUpnlZiP3pjL+JB4laIE3OyNb3bCV0qtw7MVaSOd8aqRy1QUB1Uyt/9zmh5bF...
citrix.mobile.ads.otp=7iobrh26pc9k49dl3j1f1suj
anthropic-domain-verification-459nyd=a36O4xHhvNFk8IzgJ8uNMfVWv
MS=ms20931489
Qqc2tfGoKPiJ/AObUmR9zLkG9i03lRwrNu46+01KJw/47KxNlk+Zp1BqGg5+zenWzUQc+yCir+W6RE3x...
google-site-verification=mEP4E68t0nOu1yoRhxarjQWrA80V7ch0DHjvQpXeyMM
adobe-idp-site-verification=dce4a001508adff6a7b1ce11bcee94997898dc790dbe672077b6...
facebook-domain-verification=n7h3jw7rnv9kq2waau3d7dxparqf2o
apple-domain-verification=xUMEwQIhK0FlJVa4
9lt514stfth6lslc8vbin8mtj8
MS=ms54841113
cisco-ci-domain-verification=7ad5f2849e44c916d7097809f22d9cbe1a9ad7e0c1869719387...
openai-domain-verification=dv-ZkUJHAixIasL3TvCWNzWW5zc
CAALookup not available with standard resolver
Resolved in 154 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 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 610 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 610 B Sitemaps referenced 2 User-agents Twitterbot, * Blocking No — crawling allowed
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 Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.pewtrusts.org/
200https://pewtrusts.org/

Preferred variant: non-www

HTTP → HTTPS

301http://pewtrusts.org/ https://www.pewtrusts.org/

Consistent

A+
Domain Intelligence
pewtrusts.org — via eNom, LLC, 26 years, 6 months old, hosted on Microsoft Azure
PASS
pewtrusts.org — via eNom, LLC, 26 years, 6 months old, hosted on Microsoft Azure
Info::
Domain registered until Feb 15, 2027 (9 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: eNom, LLC
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: Microsoft Azure
Got: AS8075
Domain expiry

247 days

February 15, 2027

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

26 years, 6 months

Registered February 15, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

104.45.130.11

Registrar

eNom, LLC

Unlocked 5 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 eNom, LLC
Created February 15, 2000 (26 years, 6 months ago)
Expires February 15, 2027 (9 months)
Last Updated January 22, 2026
Name Servers pdns68.ultradns.org, pdns68.ultradns.co.uk, pdns68.ultradns.com, pdns68.ultradns.info, pdns68.ultradns.net
DNSSEC Not enabled
Hosting
IP Address 104.45.130.11
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.5s)

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 458 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
208 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
458 ms
Total Time Total request time from DNS lookup through full response.
458 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 98 ms TLS Handshake 208 ms Server Processing 102 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