Skip to content
https://wikimediafoundation.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
11 PASS 6 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 192.0.66.2: lookup 192.0.66.2: 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 2a04:fa87:fffd::c000:4280: lookup 2a04:fa87:fffd::c000:4280: 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
HTTP Probe Timing
Total 915 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 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.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
776 ms
Total Time Total request time from DNS lookup through full response.
916 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 0 ms TLS Handshake 7 ms Server Processing 742 ms Content Transfer 139 ms
B
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host api.mapbox.com, 3 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host api.mapbox.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (api.mapbox.com, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: x-amz-cf-id: vxnEIpENI4-n9Ltt840ddOy8JT8nhYuy2RiJfV24ZxupqjNZSsXsZA==
Info::
Assets on AWS CloudFront: api.mapbox.com (assets: 3), cache Hit from cloudfront
Got: x-amz-cf-id: vxnEIpENI4-n9Ltt840ddOy8JT8nhYuy2RiJfV24ZxupqjNZSsXsZA==
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • api.mapbox.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • piwik.wikimedia.org — assets: 2 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a04:fa87:fffd::c000:4280
Info::
3 nameserver(s) configured
Got: ns1.wikimedia.org, ns0.wikimedia.org, ns2.wikimedia.org
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 29 ms
Got: 29 ms
A192.0.66.2
AAAA2a04:fa87:fffd::c000:4280
CNAME—
NSns1.wikimedia.org, ns0.wikimedia.org, ns2.wikimedia.org
MX
10 mx-in2001.wikimedia.org
10 mx-in1001.wikimedia.org
TXT
SPF v=spf1 include:wikimedia.org ~all
google-site-verification=M_SODfP3BPr-z8R-YmIdrbm_nEJDG6BpfRXsf-e6P8E
google-site-verification=m7jEgoI4DOUy0u6cebxtp7oJT7s3nnNyPWgmPQmNEjc
facebook-domain-verification=orjhfudqyeumf4uber3bpwan5pisu0
CAALookup not available with standard resolver
Resolved in 29 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
CAA Records
issue: letsencrypt.org, pki.goog | iodef configured
PASS
issue: letsencrypt.org, pki.goog | iodef configured
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org, pki.goog
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A
Multi-Resolver DNS Speed
Mean 52ms across 3 resolvers (spread 97ms)
PASS
Mean 52ms across 3 resolvers (spread 97ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 114ms
Got: 114ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://wikimediafoundation.org

https://wikimediafoundation.org

688 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wikimediafoundation.org200688 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a04:fa87:fffd::c000:4280
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a04:fa87:fffd::c000:4280 Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 1741 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1741 B Sitemaps referenced 26 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://wikimediafoundation.org/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ar/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/zh-hant/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/fr/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ru/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/es/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/de/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/it/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ja/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/nl/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/cs/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/sv/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/da/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/nb/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/el/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/pl/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/zh-hans/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ca/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/hu/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/lv/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ro/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/sk/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/uk/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/vi/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/he/sitemap_index.xml
Sitemap: https://wikimediafoundation.org/ms/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 4 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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.wikimediafoundation.org/
200https://wikimediafoundation.org/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
wikimediafoundation.org — via MarkMonitor Inc., 23 years, 7 months old
PASS
wikimediafoundation.org — via MarkMonitor Inc., 23 years, 7 months old
Info::
Domain registered until Jul 19, 2027 (8 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: MarkMonitor 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

249 days

July 19, 2027

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

23 years, 7 months

Registered July 19, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:fa87:fffd::c000:4280

Registrar

MarkMonitor Inc.

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 19, 2003 (23 years, 7 months ago)
Expires July 19, 2027 (8 months)
Last Updated August 12, 2026
Name Servers ns0.wikimedia.org, ns1.wikimedia.org, ns2.wikimedia.org
DNSSEC Not enabled
Hosting
IP Address 2a04:fa87:fffd::c000:4280
Data source: rdap (0.4s)

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+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=MISS
A+
Health Check Endpoint
Health endpoint at https://wikimediafoundation.org/health (HTTP 200)
PASS
Health endpoint at https://wikimediafoundation.org/health (HTTP 200)
Info::
Public health endpoint at https://wikimediafoundation.org/health
Got: https://wikimediafoundation.org/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback