E-commerce infrastructure is a chain of dependencies where a single missing link — an expired cert on checkout.example.com, a DMARC misconfig that sends order confirmations to spam, a subdomain takeover that phishes returning customers — takes the whole business offline.
The famous stories should be enough:
- Ericsson / O2 / SoftBank JP (December 2018) — expired software cert took 32M+ mobile subscribers offline for a working day across 11 countries. O2 pursued Ericsson for ~£100M in damages.
- Microsoft Teams (February 2020) — 20M DAU offline for ~3 hours from an expired auth cert.
- Spotify
*.wg.spotify.com(August 2020) — global 1-hour outage on wildcard-cert expiry;#spotifydowntrended. - Keyfactor 2024 PKI Report — 86% of organizations hit at least one cert-related outage in the past 12 months. 10% every week.
None of these were caused by attackers. They were caused by forgotten renewals.
What Makes This Worse (2026-2029)
The CA/Browser Forum SC-081v3 timeline cuts TLS cert lifetime:
- March 2026 — max 200 days
- 2027 — max 100 days
- 2029 — max 47 days
That’s 8× more renewals per domain than today. Manual tracking already breaks at scale. At 47 days it’s untenable.
Simultaneously, PCI DSS 4.0.1 Req 5.4.1 (effective March 2025) mandated automated anti-phishing controls for any organization storing, processing, or transmitting cardholder data. DMARC / SPF / DKIM / MTA-STS are named as example implementations. Your QSA will ask about them.
The E-commerce Domain Surface
Every checkout-adjacent domain matters. Typical inventory:
- Root —
example.com - Checkout —
checkout.example.comorsecure.example.com - Admin —
admin.example.com,login.example.com - API —
api.example.com - CDN —
cdn.example.com,static.example.com - Marketing subdomains —
blog.example.com,learn.example.com - Email sending —
mail.example.com, transactional-domain likereceipts.example.com - Legacy — old sites still resolving, dangling CNAMEs from decommissioned services
Each has its own cert, its own DNS, its own DMARC posture. Each is a single-point-of-failure for something.
The DomainScan Setup for E-commerce
1. Full inventory
Add every domain and subdomain used for anything commerce-related. DomainScan’s subdomain enumeration catches the ones you forgot.
2. Trust Score baseline
Get a composite trust score per domain. Establish a floor. Alert on any drop.
3. SSL lifecycle automation
Every cert watched from issuance through renewal to expiry. 30/14/7/1-day alerts. Route to your on-call.
4. DMARC to p=reject
Progress from p=none (monitor) to p=quarantine to p=reject for every sending domain. Order confirmations, receipts, marketing — none should be spoofable. See how to set up DMARC.
5. CAA enforcement
Publish CAA records restricting cert issuance to your approved CAs. Blocks rogue-cert attacks that could enable checkout MitM.
6. Security headers deployment
HSTS, CSP, X-Frame-Options, Permissions-Policy — deployed carefully to lock down the browser-side attack surface without breaking legitimate embeds.
7. Continuous audit
The above runs continuously. When anything drifts — new DNS record appears, cert renewal window opens, DMARC alignment breaks, subdomain becomes takeoverable — you know before your customer does.
Bottom Line
E-commerce infrastructure fails silently. Renewal emails go to admin@ that nobody reads. CDN configs drift. Marketing adds an ESP without telling IT. Someone deletes the DNS record for the promo subdomain but leaves the CNAME pointing at Heroku.
DomainScan surfaces every one of these before it costs a checkout minute.
Related
Read what an SSL certificate is, the cost of downtime primer, and the CAA record deep dive.