Skip to content
https://matrix.to

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 1470 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 1470 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!DOCTYPE html><html><head>
    <meta charset="utf-8">
    <title>You&apos;re invited to talk on Matrix</title>
    <meta name="description" content="You&apos;re invited to talk on Matrix">
    <meta name="viewport" content="width=device-width, user-scalable=no">
    <link rel="stylesheet" type="text/css" href="bundle-404453117.css">
    <meta property="twitter:card" content="summary">
    <meta property="twitter:image" content="https://matrix.org/blog/img/matrix-logo.png">
	<meta property="twitter:site" content="@matrixdotorg">
	<meta property="twitter:title" content="Matrix - Decentralised and secure communication">
	<meta property="twitter:description" content="You&apos;re invited to talk on Matrix. If you don&apos;t already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation">
</head>
<body>
    <script type="text/javascript">window.regeneratorRuntime = undefined;</script><script type="text/javascript" src="bundle-4193300336.js"></script><script type="text/javascript">bundle.main(document.body);</script>
    <noscript>
        <h1>Please enable javascript</h1>
        <p>Matrix.to is a preview service from chat rooms, people and communities on <a href="https://matrix.org">Matrix</a>.</p>
        <p>It preserves your privacy by only processing what you view on the client side. For this to work, it needs javascript.</p>
    </noscript>


</body></html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
2 A records, 42 ms lookup
PASS
2 A records, 42 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.129.62, 104.21.2.132
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::ac43:813e, 2606:4700:3035::6815:284
Info::
2 nameserver(s) configured
Got: derek.ns.cloudflare.com, laura.ns.cloudflare.com
Info::
1 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: 42 ms
Got: 42 ms
A172.67.129.62, 104.21.2.132
AAAA2606:4700:3034::ac43:813e, 2606:4700:3035::6815:284
CNAME
NSderek.ns.cloudflare.com, laura.ns.cloudflare.com
MX
0
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 42 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://matrix.to

https://matrix.to

95 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://matrix.to20095 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::ac43:813e, 2606:4700:3035::6815:284
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::ac43:813e, 2606:4700:3035::6815:284 Connection Reachable (17 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

522https://www.matrix.to/
200https://matrix.to/

HTTP → HTTPS

301http://matrix.to/ https://matrix.to/

Consistent

A+
Domain Intelligence
matrix.to — via Government of Kingdom of Tonga, 10 years, 9 months old
PASS
matrix.to — via Government of Kingdom of Tonga, 10 years, 9 months old
Info::
Domain registered until Sep 15, 2027 (1 years, 5 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: Government of Kingdom of Tonga
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

394 days

September 15, 2027

SSL certificate

86 days

Issued by Google Trust Services

Domain age

10 years, 9 months

Registered September 15, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::6815:284

Registrar

Government of Kingdom of Tonga

Unlocked 2 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 Government of Kingdom of Tonga
Created September 15, 2015 (10 years, 9 months ago)
Expires September 15, 2027 (1 years, 5 months)
Last Updated September 2, 2022
Name Servers derek.ns.cloudflare.com, laura.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3035::6815:284
Data source: rdap (0.7s)

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

Connection waterfall

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

Send Feedback