Security checks — sorted by severity
DMARC / Email Security
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Cookie Security
Strengths: 7 cookie(s) analyzed; All cookies have SameSite attribute. Issues: 4/7 cookie(s) missing Secure flag (localization, cart_currency, _shopify_y...); 4/7 cookie(s) missing HttpOnly flag (localization, cart_currency, _shopify_y...).
Strengths: 7 cookie(s) analyzed; All cookies have SameSite attribute. Issues: 4/7 cookie(s) missing Secure flag (localization, cart_currency, _shopify_y...); 4/7 cookie(s) missing HttpOnly flag (localization, cart_currency, _shopify_y...).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
DNS CAA Records
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 2 nameservers configured (ns20.domaincontrol.com, ns19.domaincontrol.com); SOA record present and MNAME consistent with NS set; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (domaincontrol.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 2 nameservers configured (ns20.domaincontrol.com, ns19.domaincontrol.com); SOA record present and MNAME consistent with NS set; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (domaincontrol.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
HSTS Header
HSTS configured with max-age=7889238s (91 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
HSTS configured with max-age=7889238s (91 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: no default-src fallback directive; X-XSS-Protection: '1; mode=block' — this header is deprecated and removed from Chrome, Firefox, and Edge. Non-zero values introduce timing side-channel risks; set to '0' or remove the header entirely.
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: no default-src fallback directive; X-XSS-Protection: '1; mode=block' — this header is deprecated and removed from Chrome, Firefox, and Edge. Non-zero values introduce timing side-channel risks; set to '0' or remove the header entirely.
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.
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
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
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.
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.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt; 166 certificates logged in CT; Certificates from 3 CAs: Amazon, Google Trust Services, Let's Encrypt.
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt; 166 certificates logged in CT; Certificates from 3 CAs: Amazon, Google Trust Services, Let's Encrypt.
Recommended actions
1+ items
Steps to improve scoopwholefoodsshop.com's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF, DKIM)
DMARC / Email Security
Without email authentication, anyone can send emails that appear to come from scoopwholefoodsshop.com. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF, DKIM are not configured.
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
See all 3 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
scoopwholefoodsshop.com scored 72/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security, Cookie Security. Positive signals: MX Records & Mail Provider, TLS Protocol Support, TLS Configuration all passed.
4 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How scoopwholefoodsshop.com compares
Grade distribution across 2685 companies we've scanned. scoopwholefoodsshop.com scores better than 46% of them.
88
A+
28
A
196
A-
202
B+
76
B
376
B-
138
C+
117
C
347
C-
123
D+
96
D
266
D-
632
F
scoopwholefoodsshop.com — Grade C- (72/100)
2685 companies scanned
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS configured with max-age=7889238s (91 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.
SSL Certificate
Valid
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt; 166 certificates logged in CT; Certificates from 3 CAs: Amazon, Google Trust Services, Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns20.domaincontrol.com, ns19.domaincontrol.com); SOA record present and MNAME consistent with NS set; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (domaincontrol.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Similar companies
Other domains with comparable security profiles.
