Skip to content
https://yoast.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
14
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
14 PASS 3 REVIEW
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.18.32.250: lookup 104.18.32.250: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.64.155.6: lookup 172.64.155.6: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2a06:98c1:3100::6812:20fa: lookup 2a06:98c1:3100::6812:20fa: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:440c::ac40:9b06: lookup 2606:4700:440c::ac40:9b06: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.32.250, 172.64.155.6
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3100::6812:20fa, 2606:4700:440c::ac40:9b06
Info::
2 nameserver(s) configured
Got: noah.ns.cloudflare.com, michelle.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A104.18.32.250, 172.64.155.6
AAAA2a06:98c1:3100::6812:20fa, 2606:4700:440c::ac40:9b06
CNAME
NSnoah.ns.cloudflare.com, michelle.ns.cloudflare.com
MX
1 yoast-com.mail.protection.outlook.com
TXT
MS=ms78685604
Z3qBVG59qHmN9/lxOB6rZvFnW07XoQpUr1m3NNidUTs=
openai-domain-verification=dv-QVbniSWRe6FPSCd8XMkPSfGK
facebook-domain-verification=86uvc5980643pknxh7zh6ubsch1be3
google-site-verification=5fk1rgHgsRBL4zF9J22BTHatklicABBD2u9PiYjG29c
google-site-verification=UIM9RxPitiw_QZ6DWa-DJrgiL6xN6B8qtwTT1TzRy3k
google-site-verification=VH2W1c57ncgMkRuSXwDjXWG4M6TLQNcFK0VmWsF9uyE
google-site-verification=ZeQqi72uJEHU2igUGGYFqyBusMuawaAuaqzTkGO3CvQ
google-site-verification=m3RQqR4eW1BsnuoNhE4cC5in3LK9H9DKv_iwhoDjEwM
google-site-verification=nsTjyg2Yxp4qMZwjzE9c880aGsdXyuTVSausZY76PWs
google-site-verification=omOoCAQCaPA-sw2aR2DaVaBkYf929VYJTAwOzOHFFUc
google-site-verification=pokWAvijRJd6ZVb3f8xkmyJa2yyptsoMj_bqQQGY7Cc
google-site-verification=vg7XQpZ7Jx981kNJlyCONodaJ1FDFvpfF3ZnMJylelQ
prowly-verification=d23b5db23f86c15e0d50137c6a5fd56e4ed19210d865f4346487126e0a64...
SPF v=spf1 include:_spf.google.com include:spf.mtasv.net include:helpscoutemail.com ...
CAALookup not available with standard resolver
Resolved in 9 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
CAA Records
issue: comodoca.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog | issuewild: comodoca.com, digicert.com, globalsign.com, letsencrypt.org
PASS
issue: comodoca.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog | issuewild: comodoca.com, digicert.com, globalsign.com, letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 3ms across 3 resolvers (spread 4ms)
PASS
Mean 3ms across 3 resolvers (spread 4ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 3ms
Got: 3ms via 9.9.9.9:53
Info::
Google: 6ms
Got: 6ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://yoast.com

https://yoast.com

42 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yoast.com20042 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3100::6812:20fa, 2606:4700:440c::ac40:9b06
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3100::6812:20fa, 2606:4700:440c::ac40:9b06 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 927 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
Sitemap index with 19 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 927 B Sitemaps referenced 1 User-agents WikiDo, Gigabot, Barkrowler, BLEXBot, magpie-crawler, Nuclei, Riddler, PetalBot, Zoominfobot, Go-http-client, Node/simplecrawler, CazoodleBot, dotbot/1.0, * Blocking No — crawling allowed
# If you want to learn about why our robots.txt looks like this, read this post: https://yoa.st/robots-txt

# Global rules
# -----------------
User-agent: *
Disallow: /wp-json/

# We're experimenting with blocking search results to prevent search result spam
Disallow: /?s=*
Disallow: /search/*

# Prevent crawling CF challenge URLs
Disallow: /cdn-cgi/bm/cv/
Disallow: /cdn-cgi/challenge-platform/

# Sitemap
# -----------------
Sitemap: https://yoast.com/sitemap_index.xml
Schemamap: https://yoast.com/wp-json/yoast/v1/schema-aggregator/get-xml

# Ban bots that don't benefit us.
# --------------------------------

User-agent: Nuclei
User-agent: WikiDo
User-agent: Riddler
User-agent: PetalBot
User-agent: Zoominfobot
User-agent: Go-http-client
User-agent: Node/simplecrawler
User-agent: CazoodleBot
User-agent: dotbot/1.0
User-agent: Gigabot
User-agent: Barkrowler
User-agent: BLEXBot
User-agent: magpie-crawler
Disallow: /

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.yoast.com/
200https://yoast.com/

Preferred variant: non-www

HTTP → HTTPS

301http://yoast.com/ https://yoast.com/

Consistent

A+
Domain Intelligence
yoast.com — via NameCheap, Inc., 26 years, 6 months old
PASS
yoast.com — via NameCheap, Inc., 26 years, 6 months old
Info::
Domain registered until Mar 22, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: NameCheap, 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.
Domain expiry

311 days

March 22, 2027

SSL certificate

73 days

Issued by Google Trust Services

Domain age

26 years, 6 months

Registered March 22, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3100::6812:20fa

Registrar

NameCheap, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created March 22, 2000 (26 years, 6 months ago)
Expires March 22, 2027 (10 months)
Last Updated February 20, 2026
Name Servers michelle.ns.cloudflare.com, noah.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2a06:98c1:3100::6812:20fa
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 29 ms Content Transfer 2 ms
A+
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires
PASS

Certificate validity

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

Recommended actions

No action required — TLS configuration looks healthy.

A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9f8f5b152d44cd4e-GRU
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f8f5b152d44cd4e-GRU
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=1697, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback