Skip to content
https://prospect.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
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

C
TLS Certificate Expiry & Recommendations
Action
29 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

29
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 29 days remaining
  • 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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 192.0.78.220, 192.0.78.178
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.wordpress.com, ns1.wordpress.com, ns3.wordpress.com
Info::
7 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: 45 ms
Got: 45 ms
A192.0.78.220, 192.0.78.178
AAAA—
CNAME—
NSns2.wordpress.com, ns1.wordpress.com, ns3.wordpress.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx5.googlemail.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
30 aspmx4.googlemail.com
TXT
google-site-verification=DHMSkKDAnyF-Q3JmkJWTxUCgxIVmefzujnHFw5u4XQo
ZOOM_verify_elSDEqCuICBLjxbmD2zDuw
SPF v=spf1 include:_spf.google.com include:_spfprod.ngpvan.com include:emsd1.com ~al...
atomic-domain-e6aecb4d40046c90d4e24db63978d3e1d23dbc65fdcc54056f1cab9318a3c608
stripe-verification=ef9d5af876c6e02fb52c5e62b826b71b1f607074c48b40ec72ef6c269534...
CAALookup not available with standard resolver
Resolved in 45 ms

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://prospect.org

https://prospect.org

8 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://prospect.org2008 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 40 URLs
PASS
robots.txt present, sitemap with 40 URLs
Info::
robots.txt is present
Got: 481 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 40 entries
Info::
Sitemap index with 40 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 481 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
Sitemap: https://prospect.org/sitemap.xml
Sitemap: https://prospect.org/news-sitemap.xml
User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 40 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.prospect.org/
200https://prospect.org/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
prospect.org — via Network Solutions, LLC, 30 years old, hosted on WordPress.com (Automattic)
PASS
prospect.org — via Network Solutions, LLC, 30 years old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Sep 19, 2027 (1 years, 5 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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

460 days

September 19, 2027

SSL certificate

29 days

Issued by Let's Encrypt

Domain age

30 years

Registered September 20, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.78.220

Registrar

Network Solutions, LLC

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created September 20, 1996 (30 years ago)
Expires September 19, 2027 (1 years, 5 months)
Last Updated September 11, 2025
Name Servers ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
DNSSEC Not enabled
Hosting
IP Address 192.0.78.220
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
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 561 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
318 ms
Total Time Total request time from DNS lookup through full response.
561 ms

Connection waterfall

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

Send Feedback