Infrastructure - https://pytorch.org BeaverCheck Audit

B

TLS Certificate Expiry & Recommendations

38 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

38

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, 168 ms lookup

PASS

1 A records, 168 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.185.0.2

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 2 IPv6 (AAAA) record(s)

Got: 2620:12a:8000::2, 2620:12a:8001::2

4 nameserver(s) configured

Got: ns1.dnsimple.com, ns2.dnsimple-edge.net, ns3.dnsimple.com, ns4.dnsimple-edge.org

5 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 168 ms

Got: 168 ms

A	23.185.0.2
AAAA	2620:12a:8000::2, 2620:12a:8001::2
CNAME	—
NS	ns1.dnsimple.com, ns2.dnsimple-edge.net, ns3.dnsimple.com, ns4.dnsimple-edge.org
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	SPF v=spf1 include:_spf.google.com include:8112310.spf10.hubspotemail.net -all 1password-site-verification=4T2FDYHJ5JH5JJ2OSNCZDCG6PM google-site-verification=1BXngDldsKTI_vBnqZo1VCUkNdjBRHCcVFlRz3Ug52Q google-site-verification=3F-PZoqNvpZVvJYE2cPj3R3bd_1h4O6A5pwob8tAFSM google-site-verification=VWrQMOnetbh2T1g1CQano5I1c64jPAG7kdzY07hjq2s
CAA	Lookup not available with standard resolver

Resolved in 168 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

Got: https://pytorch.org

https://pytorch.org

171 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://pytorch.org	200	171 ms	HTTP/1.1	nginx

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2620:12a:8000::2, 2620:12a:8001::2

Got: 1 ms connect

IPv6 Ready

AAAA Records 2620:12a:8000::2, 2620:12a:8001::2 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 14 URLs

PASS

robots.txt present, sitemap with 14 URLs

robots.txt is present

Got: 112 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 14 entries

Sitemap index with 14 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 112 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://pytorch.org/wp-sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 14 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.pytorch.org/

200https://pytorch.org/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

pytorch.org — via 1API GmbH, 9 years, 9 months old

PASS

pytorch.org — via 1API GmbH, 9 years, 9 months old

Domain registered until Aug 15, 2026 (3 months remaining)

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.

Registrar: 1API GmbH

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

63 days

August 15, 2026

SSL certificate

38 days

Issued by Let's Encrypt

Domain age

9 years, 9 months

Registered August 15, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8001::2

Registrar

1API GmbH

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar 1API GmbH

Created August 15, 2016 (9 years, 9 months ago)

Expires August 15, 2026 (3 months)

Last Updated November 25, 2025

Name Servers ns1.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple-edge.org, ns2.dnsimple-edge.net

DNSSEC Not enabled

Hosting

IP Address 2620:12a:8001::2

Data source: rdap (0.3s)

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 183 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

166 ms

TCP Connect

1 ms

TLS Handshake

6 ms

Time to First Byte

179 ms

Total Time

183 ms

Connection waterfall

DNS Lookup 166 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 7 ms Content Transfer 4 ms

A+

CDN & Delivery

Fastly (HIT, HIT, MISS, MISS)

PASS

Fastly (HIT, HIT, MISS, MISS)

Site is served via Fastly CDN

Got: x-served-by: cache-chi-kigq8000161-CHI, cache-rtm-ehrd2290024-RTM, cache-rtm-ehrd2290041-RTM, cache-rtm-ehrd2290041-RTM

CDN cache status: HIT, HIT, MISS, MISS

CDN Detected: Fastly

Provider Fastly Cache Status HIT, HIT, MISS, MISS Evidence x-served-by: cache-chi-kigq8000161-CHI, cache-rtm-ehrd2290024-RTM, cache-rtm-ehrd2290041-RTM, cache-rtm-ehrd2290041-RTM