Digital exposure report
matomo.org
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS matomo.org
- 2.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://matomo.org/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- matomo.org
- Website request
- GET https://matomo.org/
- Scan time
- 2026-11-19 02:59:59 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 27/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 23/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowReferrer-Policy · Hardening gap+3
- 3.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 6 of 10 DNS lookups.
v=spf1 include:spf.protection.outlook.com include:_spf.alwaysdata.com include:helpscoutemail.com include:spf.em.secureserver.net include:spf.discoursehosting.com include:22519270.spf08.hubspotemail.net ~all
$ dig +short TXT matomo.org
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1;p=quarantine;sp=reject;rua=mailto:sipgu9rh@ag.au.dmarcian.com,mailto:dmarc-report@matomo.org;ruf=mailto:dmarc-failure@matomo.org;fo=d
$ dig +short TXT _dmarc.matomo.org
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: selector1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmgQBCgEH/zVsEXqxvm6CsTnKqCur… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAk8zCBHAOxFmwjI5USyhLva0xdKa4ZTsz… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDOHyf5HFNekQS1RrQrbEjGuWx8jS8/16NbBy59…
$ dig +short TXT selector1._domainkey.matomo.org
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
0 matomo-org.mail.protection.outlook.com
$ dig +short MX matomo.org
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://matomo.org/ returned HTTP 200 (final URL: https://matomo.org/). Client-side certificate validation passed.
HTTP 200 Final URL: https://matomo.org/
$ curl -sIL https://matomo.org/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://matomo.org/
HTTP 301 Location: https://matomo.org/
$ curl -sI http://matomo.org/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: Amazon Trust Services, expiring 2027-03-01 (102 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Amazon Trust Services Valid from: 2026-01-31 Valid until: 2027-03-01 Names: *.matomo.org, matomo.org Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect matomo.org:443 -servername matomo.org 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=63072000 (730 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000;
$ curl -sIL https://matomo.org/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval' — weakens XSS protection.
Content-Security-Policy: default-src 'none'; form-action 'self' https://login.microsoftonline.com https://madmimi.com https://cdn.jsdelivr.net https://www.facebook.com; frame-ancestors 'self' https://*.matomo.cloud https://*.innocraft.cloud http://localhost; base-uri 'self' https://demo-web.matomo.org https://web.innocraft.cloud; connect-src 'self' https://matomo.org https://web.innocraft.cloud https://www.userlike.com https://cdn.plyr.io https://demo-web.matomo.org https://userlike-cdn-widgets.s3-eu-west-1.amazonaws.com wss://chat.userlike.com wss://umd.userlike.com https://api.userlike.com https://video.matomo.org https://api.usercentrics.eu https://consent-api.service.consent.usercentrics.eu https://v1.api.service.cmp.usercentrics.eu https://privacy-proxy.usercentrics.eu https://graphql.usercentrics.eu; script-src 'self' https://snap.licdn.com https://userlike-cdn-umm.b-cdn.net https://web.innocraft.cloud https://cdn.matomo.cloud https://embed.clickmeeting.com https://madmimi.com https://cdn.shortpixel.ai https://cdnjs.cloudflare.com https://www.youtube.com api.userlike.com https://d3dc1lgancj6l0.cloudfront.net https://userlike-cdn-widgets.s3-eu-west-1.amazonaws.com https://demo-web.matomo.org https://m-img.org 'unsafe-eval' 'unsafe-inline' https://app.usercentrics.eu https://api.usercentrics.eu https://web.cmp.usercentrics.eu https://privacy-proxy.usercentrics.eu; style-src 'self' 'unsafe-inline' https://demo-web.matomo.org https://web.innocraft.cloud https://app.usercentrics.eu https://ams.wpml.org; img-src 'self' https://*.matomo.org https://demo-web.matomo.org https://web.innocraft.cloud https://plugins.matomo.org https://qrcode.kaywa.com https://raw.githubusercontent.com https://user-images.githubusercontent.com https://m-img.org https://piwik.org https://matomo.org https://video.matomo.org https://app.usercentrics.eu https://uct.service.usercentrics.eu api.userlike.com https://userlike-cdn-operators.userlike.com userlike-cdn-operators.s3-eu-west-1.amazonaws.com data:; media-src 'self' https://video.matomo.org https://www.matomo.org https://matomo.org blob:; font-src 'self' https://matomo.org https://*.matomo.org https://userlike-cdn-umm.b-cdn.net https://demo-web.matomo.org https://web.innocraft.cloud data: https://github.com https://d3dc1lgancj6l0.cloudfront.net; frame-src 'self' blob: https://matomo.org https://www.facebook.com https://play.quickchannel.com https://matomo.clickmeeting.com https://embed.clickmeeting.com https://www.youtube-nocookie.com https://demo.matomo.cloud https://demo-web.matomo.org https://demo2.piwik.org https://demo2.matomo.org https://app.usercentrics.eu https://web.cmp.usercentrics.eu;
$ curl -sIL https://matomo.org/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
frame-ancestors 'self' https://*.matomo.cloud https://*.innocraft.cloud http://localhost
X-Frame-Options: (missing) CSP frame-ancestors: 'self' https://*.matomo.cloud https://*.innocraft.cloud http://localhost
$ curl -sIL https://matomo.org/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://matomo.org/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://matomo.org/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(), ambient-light-sensor=(), autoplay=(self), battery=(), camera=(), display-capture=(), document-domain=(self), encrypted-media=(), fullscreen=(s
Permissions-Policy: accelerometer=(), ambient-light-sensor=(), autoplay=(self), battery=(), camera=(), display-capture=(), document-domain=(self), encrypted-media=(), fullscreen=(self "https://video.matomo.org"), gamepad=(), geolocation=(), gyroscope=(), layout-animations=(), legacy-image-formats=(), magnetometer=(), microphone=(), midi=(), oversized-images=(self), payment=(), picture-in-picture=("https://video.matomo.org"), publickey-credentials-get=(), screen-wake-lock=(), speaker-selection=(), unoptimized-images=(self "https://m.img.org"), sync-xhr=(self), usb=()$ curl -sIL https://matomo.org/ | grep -i "Permissions-Policy"
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://matomo.org/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS matomo.org: NODATA
$ dig +short DS matomo.org
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec matomo.org SOA delv matomo.org
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issuewild "amazonaws.com" | 0 issuewild "letsencrypt.org"
0 issuewild "amazonaws.com" 0 issuewild "letsencrypt.org"
$ dig +short CAA matomo.org
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns-1081.awsdns-07.org ns-1635.awsdns-12.co.uk ns-516.awsdns-00.net ns-85.awsdns-10.com
$ dig +short NS matomo.org
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | matomo.org | 18.155.75.109 | 18.155.75.118 | 18.155.75.48 | 18.155.75.74 |
| AAAA | matomo.org | 2600:9000:2106:d600:1e:6cc8:7300:93a1 | 2600:9000:2106:a800:1e:6cc8:7300:93a1 | 2600:9000:2106:3000:1e:6cc8:7300:93a1 | 2600:9000:2106:2200:1e:6cc8:7300:93a1 | 2600:9000:2106:1600:1e:6cc8:7300:93a1 | 2600:9000:2106:5600:1e:6cc8:7300:93a1 | 2600:9000:2106:9000:1e:6cc8:7300:93a1 | 2600:9000:2106:da00:1e:6cc8:7300:93a1 |
| MX | matomo.org | 0 matomo-org.mail.protection.outlook.com |
| NS | matomo.org | ns-1081.awsdns-07.org | ns-1635.awsdns-12.co.uk | ns-516.awsdns-00.net | ns-85.awsdns-10.com |
| TXT | matomo.org | MS=ms49514484 | atlassian-domain-verification=M0nlYa9s3/Rq/yjkvft8qrZwX5l8I+72RXK+mh7T4U7AYtbrz8Sn6BzjGsGWNOzd | knowbe4-site-verification=cdf4795af74c51da9c2f2b6d81906eb9 | openai-domain-verification=dv-2ZeMsWvHS7133e1AzKxbcjjQ | v=spf1 include:spf.protection.outlook.com include:_spf.alwaysdata.com include:helpscoutemail.com include:spf.em.secureserver.net include:spf.discoursehosting.com include:22519270.spf08.hubspotemail.net ~all |
| TXT | _dmarc.matomo.org | v=DMARC1;p=quarantine;sp=reject;rua=mailto:sipgu9rh@ag.au.dmarcian.com,mailto:dmarc-report@matomo.org;ruf=mailto:dmarc-failure@matomo.org;fo=d |
| CAA | matomo.org | 0 issuewild "amazonaws.com" | 0 issuewild "letsencrypt.org" |
| DS | matomo.org | — |