Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
pinterest.com scored 98/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
1 action item identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How pinterest.com compares
Grade distribution across 2385 companies we've scanned. pinterest.com scores better than 97% of them.
72
A+
22
A
180
A-
181
B+
69
B
333
B-
114
C+
111
C
297
C-
110
D+
92
D
216
D-
588
F
pinterest.com — Grade A+ (98/100)
2385 companies scanned
Security checks
Each check inspects a different part of pinterest.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 4 cookie(s) analyzed. Issues: 1/4 cookie(s) missing Secure flag (_routing_id); 1/4 cookie(s) missing HttpOnly flag (csrftoken); 2/4 cookie(s) missing SameSite attribute (_auth, _routing_id).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
Strengths: CAA records configured (1 record(s)); Authorized CAs: digicert.com; cansignhttpexchanges=yes. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Strengths: 4 nameservers configured (ns9.pinterest.com., ns5.pinterest.com., ns6.pinterest.com., ns10.pinterest.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present; DKIM configured (selectors: google).
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 149 days remaining; Issued by DigiCert Inc; 367 certificates logged in CT; Certificates from 7 CAs: "DigiCert, "GoDaddy.com, Cybertrust Inc. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1 item
Steps to improve pinterest.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for pinterest.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec pinterest.com
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present; DKIM configured (selectors: google).
SPF Record
Present
v=spf1 redirect=_spf.pinterest.com
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 149 days remaining; Issued by DigiCert Inc; 367 certificates logged in CT; Certificates from 7 CAs: "DigiCert, "GoDaddy.com, Cybertrust Inc. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns9.pinterest.com., ns5.pinterest.com., ns6.pinterest.com., ns10.pinterest.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.