Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
chipy.com scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: MX Records & Mail Provider, DNS 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 chipy.com compares
Grade distribution across 2436 companies we've scanned. chipy.com scores better than 88% of them.
75
A+
24
A
183
A-
186
B+
70
B
342
B-
117
C+
111
C
307
C-
113
D+
93
D
220
D-
595
F
chipy.com — Grade A- (90/100)
2436 companies scanned
Security checks
Each check inspects a different part of chipy.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
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
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
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.
DNS Configuration
Strengths: 2 nameservers configured (dora.ns.cloudflare.com., phil.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Security Headers
4/5 security headers present. Missing: CSP.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: default, google).
Known Breaches
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.
Certificate Hygiene
Strengths: Certificate valid, 79 days remaining; Issued by Google Trust Services. 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 chipy.com's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on chipy.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://chipy.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: default, google).
SPF Record
Present
v=spf1 +mx +a +ip4:72.52.246.196 ip4:91.239.185.0/24 ip4:207.8.198.0/26 ip4:89.206.36.192/26 include
Security Headers
4/5 present
Missing: CSP
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 79 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Enabled
Strengths: 2 nameservers configured (dora.ns.cloudflare.com., phil.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.