Skip to content
https://whyy.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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 Records
1 A records, 37 ms lookup
PASS
1 A records, 37 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8001::1, 2620:12a:8000::1
Info::
4 nameserver(s) configured
Got: ns1.p201.dns.oraclecloud.net, ns2.p201.dns.oraclecloud.net, ns3.p201.dns.oraclecloud.net, ns4.p201.dns.oraclecloud.net
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: 37 ms
Got: 37 ms
A23.185.0.1
AAAA2620:12a:8001::1, 2620:12a:8000::1
CNAME—
NSns1.p201.dns.oraclecloud.net, ns2.p201.dns.oraclecloud.net, ns3.p201.dns.oraclecloud.net, ns4.p201.dns.oraclecloud.net
MX
0 whyy-org.mail.protection.outlook.com
TXT
docusign=dad5169f-5f75-4cd6-955e-d93caba2e8e6
google-site-verification=Cn3JX_LqROd3TCEmdw2jofwa-TN0LSvJINftGZX0_1c
facebook-domain-verification=nkhnrprj99ingd7upg6nqym51jc1xh
MS=ms40938454
google-site-verification=5PsM3qHWZIytRuRwxtIaeSttLq-3vCKBrO3HzXlUuXg
87c2d7c2-075c-4151-9568-fe4c6d4d2281
FAVFXCN7UQGGDOE4OU57IV1YIHOW99588A18VZU6F
google-site-verification=-yYhnAGu8R57PBtlIaYYttAn_XldkBJObkYPa0aVAww
SPF v=spf1 ip4:50.207.24.178 include:spf.protection.outlook.com include:_spf.e-activ...
CAALookup not available with standard resolver
Resolved in 37 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://whyy.org

https://whyy.org

23 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://whyy.org20023 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2620:12a:8001::1, 2620:12a:8000::1
Got: 1 ms connect
IPv6 Ready
AAAA Records 2620:12a:8001::1, 2620:12a:8000::1 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 164 URLs
PASS
robots.txt present, sitemap with 164 URLs
Info::
robots.txt is present
Got: 319 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 164 entries
Info::
Sitemap index with 164 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 319 B Sitemaps referenced 2 User-agents *, Googlebot Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-content/plugins/ 
Disallow: /wp-content/themes/
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 10

User-Agent: Googlebot
Allow: .js
Allow: .css
Disallow: /*&s=

Sitemap: https://whyy.org/sitemap_index.xml
Sitemap: https://whyy.org/news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 164 entries Valid XML Yes
Child Sitemaps:
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.whyy.org/
200https://whyy.org/

Preferred variant: non-www

HTTP → HTTPS

301http://whyy.org/ → https://whyy.org/

Consistent

A+
Domain Intelligence
whyy.org — via Network Solutions, LLC, 32 years, 2 months old
PASS
whyy.org — via Network Solutions, LLC, 32 years, 2 months old
Info::
Domain registered until Jul 18, 2027 (1 years, 3 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: Network Solutions, 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.
Domain expiry

397 days

July 18, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

32 years, 2 months

Registered July 19, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::1

Registrar

Network Solutions, LLC

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 Network Solutions, LLC
Created July 19, 1994 (32 years, 2 months ago)
Expires July 18, 2027 (1 years, 3 months)
Last Updated May 20, 2023
Name Servers ns1.p201.dns.oraclecloud.net, ns2.p201.dns.oraclecloud.net, ns3.p201.dns.oraclecloud.net, ns4.p201.dns.oraclecloud.net
DNSSEC Not enabled
Hosting
IP Address 2620:12a:8001::1
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 58 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
57 ms
Total Time Total request time from DNS lookup through full response.
59 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 14 ms Content Transfer 2 ms
A+
CDN & Delivery
Fastly (HIT, HIT, MISS, MISS)
PASS
Fastly (HIT, HIT, MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-chi-kigq8000058-CHI, cache-ewr-kewr1740039-EWR, cache-ewr-kewr1740022-EWR, cache-ewr-kewr1740022-EWR
Info::
CDN cache status: HIT, HIT, MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT, MISS, MISS Evidence x-served-by: cache-chi-kigq8000058-CHI, cache-ewr-kewr1740039-EWR, cache-ewr-kewr1740022-EWR, cache-ewr-kewr1740022-EWR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback