Skip to content
https://www.fedoraproject.org

Infrastructure

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

B
DNS Records
9 A records, 22 ms lookup
REVIEW
9 A records, 22 ms lookup
Info::
Resolves to 9 IPv4 address(es)
Got: 85.236.55.6, 38.145.32.21, 3.70.22.218, 152.2.23.103, 35.178.204.134, 38.145.32.20, 18.157.159.91, 185.141.165.254, 152.2.23.104
Info::
Has 7 IPv6 (AAAA) record(s)
Got: 2001:4178:2:1269::fed2, 2604:1580:fe00:0:dead:beef:cafe:fed1, 2606:f640:6000:651::7, 2605:bc80:3010:600:dead:beef:cafe:fed9, 2a05:d014:10:7803:8468:7fac:f199:d194, 2a05:d014:10:7803:6af9:4da5:bf50:ad83, 2a05:d01c:c6a:cc02:eee3:30f3:2341:57a6
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: wildcard.fedoraproject.org
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 22 ms
Got: 22 ms
A85.236.55.6, 38.145.32.21, 3.70.22.218, 152.2.23.103, 35.178.204.134, 38.145.32.20, 18.157.159.91, 185.141.165.254, 152.2.23.104
AAAA2001:4178:2:1269::fed2, 2604:1580:fe00:0:dead:beef:cafe:fed1, 2606:f640:6000:651::7, 2605:bc80:3010:600:dead:beef:cafe:fed9, 2a05:d014:10:7803:8468:7fac:f199:d194, 2a05:d014:10:7803:6af9:4da5:bf50:ad83, 2a05:d01c:c6a:cc02:eee3:30f3:2341:57a6
CNAMEwildcard.fedoraproject.org
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 22 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 185 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 185 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wikiold

# From: https://www.mediawiki.org/wiki/Manual:Robots.txt
# This should stop google complaining about meta tags in html output.
Disallow: /w/index.php?
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.fedoraproject.org/
200https://fedoraproject.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://www.fedoraproject.org/ → https://www.fedoraproject.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.fedoraproject.org

https://www.fedoraproject.org

105 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.fedoraproject.org200105 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (31 ms)
PASS
IPv6 reachable (31 ms)
Info::
IPv6 is configured and reachable at 2001:4178:2:1269::fed2, 2604:1580:fe00:0:dead:beef:cafe:fed1, 2606:f640:6000:651::7, 2605:bc80:3010:600:dead:beef:cafe:fed9, 2a05:d014:10:7803:8468:7fac:f199:d194, 2a05:d014:10:7803:6af9:4da5:bf50:ad83, 2a05:d01c:c6a:cc02:eee3:30f3:2341:57a6
Got: 31 ms connect
IPv6 Ready
AAAA Records 2001:4178:2:1269::fed2, 2604:1580:fe00:0:dead:beef:cafe:fed1, 2606:f640:6000:651::7, 2605:bc80:3010:600:dead:beef:cafe:fed9, 2a05:d014:10:7803:8468:7fac:f199:d194, 2a05:d014:10:7803:6af9:4da5:bf50:ad83, 2a05:d01c:c6a:cc02:eee3:30f3:2341:57a6 Connection Reachable (31 ms)
A+
Domain Intelligence
fedoraproject.org — via Nom-iq Ltd. dba COM LAUDE, 22 years, 10 months old
PASS
fedoraproject.org — via Nom-iq Ltd. dba COM LAUDE, 22 years, 10 months old
Info::
Domain registered until Sep 24, 2026 (5 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Nom-iq Ltd. dba COM LAUDE
Domain expiry

74 days

September 24, 2026

SSL certificate

202 days

Issued by DigiCert Inc

Domain age

22 years, 10 months

Registered September 24, 2003

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4178:2:1269::fed2

Registrar

Nom-iq Ltd. dba COM LAUDE

Lock status unknown 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
Registrar Nom-iq Ltd. dba COM LAUDE
Created September 24, 2003 (22 years, 10 months ago)
Expires September 24, 2026 (5 months)
Last Updated August 30, 2025
Name Servers ns01.fedoraproject.org, ns02.fedoraproject.org, ns05.fedoraproject.org, ns03.fedoraproject.org
DNSSEC Enabled
Hosting
IP Address 2001:4178:2:1269::fed2
Data source: rdap (0.6s)
A+
HTTP Probe Timing
Total 227 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
112 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
203 ms
Total Time Total request time from DNS lookup through full response.
228 ms

Connection waterfall

DNS Lookup 112 ms TCP Connect 25 ms TLS Handshake 38 ms Server Processing 28 ms Content Transfer 25 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback