Skip to content
https://winehq.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1738 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1738 B Sitemaps referenced 0 User-agents Bytespider, CCBot, CloudflareBrowserRenderingCrawler, Google-Extended, GPTBot, meta-externalagent, Amazonbot, ClaudeBot, *, Applebot-Extended Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
3 A records, 8 ms lookup
PASS
3 A records, 8 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.8.100, 104.26.9.100, 172.67.69.38
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:864, 2606:4700:20::681a:964, 2606:4700:20::ac43:4526
Info::
2 nameserver(s) configured
Got: becky.ns.cloudflare.com, carter.ns.cloudflare.com
Info::
2 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: 8 ms
Got: 8 ms
A104.26.8.100, 104.26.9.100, 172.67.69.38
AAAA2606:4700:20::681a:864, 2606:4700:20::681a:964, 2606:4700:20::ac43:4526
CNAME
NSbecky.ns.cloudflare.com, carter.ns.cloudflare.com
MX
10 mail.protonmail.ch
20 mailsec.protonmail.ch
TXT
SPF v=spf1 mx a include:_spf.protonmail.ch ?all
protonmail-verification=6b710e61f7eda5d558a3052e086629dc4ddf201c
_globalsign-domain-verification=2wRqY6IrIINLY7B8Qcp-qur9HsiRTO04g4gwsMmFy3
CAALookup not available with standard resolver
Resolved in 8 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
1 redirect(s), 337 ms total
PASS
1 redirect(s), 337 ms total
Info::
Single redirect
Got: https://winehq.org → https://www.winehq.org/ (301)
Info::
WWW normalization redirect

https://winehq.org

320 ms · HTTP/1.1

301

https://www.winehq.org/

17 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://winehq.org301320 msHTTP/1.1cloudflare
2https://www.winehq.org/40317 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:864, 2606:4700:20::681a:964, 2606:4700:20::ac43:4526
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:864, 2606:4700:20::681a:964, 2606:4700:20::ac43:4526 Connection Reachable (1 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.winehq.org/
200https://winehq.org/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
winehq.org — via Cloudflare, Inc., 25 years, 7 months old
PASS
winehq.org — via Cloudflare, Inc., 25 years, 7 months old
Info::
Domain registered until Jan 26, 2029 (2 years, 9 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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

924 days

January 26, 2029

SSL certificate

66 days

Issued by Google Trust Services

Domain age

25 years, 7 months

Registered January 26, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:864

Registrar

Cloudflare, 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 Cloudflare, Inc.
Created January 26, 2001 (25 years, 7 months ago)
Expires January 26, 2029 (2 years, 9 months)
Last Updated March 4, 2024
Name Servers becky.ns.cloudflare.com, carter.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700:20::681a:864
Data source: rdap (0.2s)

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 313 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 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.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
313 ms
Total Time Total request time from DNS lookup through full response.
314 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 1 ms TLS Handshake 9 ms Server Processing 297 ms Content Transfer 1 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9f00ab48b85a2d00-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f00ab48b85a2d00-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback