Digital exposure report
woocommerce.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 03:00 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 woocommerce.com
- 2.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://woocommerce.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- woocommerce.com
- Website request
- GET https://woocommerce.com/
- Scan time
- 2026-11-19 03:00:08 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 | 28/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 | 25/30 | The site instructs browsers to block common attacks. |
| 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.LowPermissions-Policy · Hardening gap+2
- 3.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 4 of the 10 allowed DNS lookups.
v=spf1 include:spf.efwd.registrar-servers.com include:_spf.automattic.com include:spf.mandrillapp.com include:mail.zendesk.com -all
$ dig +short TXT woocommerce.com
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; rua=mailto:dmarc-reports@automattic.com;
$ dig +short TXT _dmarc.woocommerce.com
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: k1. Confirm signing with dkim=pass in a sent message's Authentication-Results.
k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8…
$ dig +short TXT k1._domainkey.woocommerce.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mx1.dfw.automattic.com 10 mx2.ams.automattic.com
$ dig +short MX woocommerce.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://woocommerce.com/ returned HTTP 200 (final URL: https://woocommerce.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://woocommerce.com/
$ curl -sIL https://woocommerce.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://woocommerce.com/
HTTP 301 Location: https://woocommerce.com/
$ curl -sI http://woocommerce.com/ | 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: Let's Encrypt, expiring 2027-02-10 (83 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: Let's Encrypt Valid from: 2026-11-12 Valid until: 2027-02-10 Names: *.woocommerce.com, woocommerce.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect woocommerce.com:443 -servername woocommerce.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000;includeSubdomains
$ curl -sIL https://woocommerce.com/ | 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: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: upgrade-insecure-requests
$ curl -sIL https://woocommerce.com/ | 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.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://woocommerce.com/ | 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://woocommerce.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://woocommerce.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://woocommerce.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
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: WordPress VIP <https://wpvip.com>
$ curl -sIL https://woocommerce.com/ | 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 woocommerce.com: NODATA
$ dig +short DS woocommerce.com
- 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 woocommerce.com SOA delv woocommerce.com
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 "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489" | 0 issue "letsencrypt.org"
0 issuewild "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489" 0 issue "letsencrypt.org"
$ dig +short CAA woocommerce.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
3 NS servers.
ns3.automattic.com ns1.automattic.com ns2.automattic.com
$ dig +short NS woocommerce.com
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 | woocommerce.com | 192.0.66.5 |
| AAAA | woocommerce.com | — |
| MX | woocommerce.com | 10 mx1.dfw.automattic.com | 10 mx2.ams.automattic.com |
| NS | woocommerce.com | ns3.automattic.com | ns1.automattic.com | ns2.automattic.com |
| TXT | woocommerce.com | openai-domain-verification=dv-sM1uf9KhozIPdARADivHbaYT | atlassian-domain-verification=HLvi8VknRfLwuOZ7TmiaKM8GgOgai45SxxeWZddVaOBMgWielcwit/LmLXXPJm6G | google-site-verification=2MHcIVDfVolWOXcexh37v8jEWLdgAZCzETaoGLKWwzQ | google-site-verification=po17wade78W8q89EYjc6OWiK9yII07_sDFQA2iCNBLE | linkedin-site-verification=2d8bb084-205e-4c78-a2c7-f4594a06a910 | google-site-verification=zhfsb0Rpdddwpi5KA_LkFzBUROeMfyKyT2NyIwOVDNs | google-site-verification=T1xrhtKCtOWWlXAJ1G_1qJQOzgLVSiSzDWrPoECAOsc | klaviyo-site-verification=VrfsGg | v=spf1 include:spf.efwd.registrar-servers.com include:_spf.automattic.com include:spf.mandrillapp.com include:mail.zendesk.com -all | jio00pf9r52emek5m3oqa0dkrv |
| TXT | _dmarc.woocommerce.com | v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@automattic.com; |
| CAA | woocommerce.com | 0 issuewild "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489" | 0 issue "letsencrypt.org" |
| DS | woocommerce.com | — |