Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
luckypatchers.com scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, DNS Configuration, TLS Configuration 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 luckypatchers.com compares
Grade distribution across 2449 companies we've scanned. luckypatchers.com scores better than 92% of them.
75
A+
24
A
181
A-
187
B+
71
B
342
B-
118
C+
113
C
309
C-
114
D+
93
D
226
D-
596
F
luckypatchers.com — Grade A- (92/100)
2449 companies scanned
Security checks
Each check inspects a different part of luckypatchers.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
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 (10 record(s)); Authorized CAs: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com. Issues: No iodef record — CA violations won't be reported to the domain owner.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: No DMARC record found — email spoofing is not prevented.
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
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.
DNS Configuration
Strengths: 2 nameservers configured (newt.ns.cloudflare.com., fiona.ns.cloudflare.com.); DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-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.
HSTS Header
HSTS enabled: max-age=15552000s (180 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Security Headers
4/5 security headers present. Missing: CSP.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
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, 35 days remaining; Issued by Let's Encrypt; 788 certificates logged in CT; Certificates from 8 CAs: "CloudFlare, "Cloudflare, "cPanel. 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 luckypatchers.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for luckypatchers.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.luckypatchers.com
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
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 +mx +a +ip4:54.39.104.116 ~all
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 35 days remaining; Issued by Let's Encrypt; 788 certificates logged in CT; Certificates from 8 CAs: "CloudFlare, "Cloudflare, "cPanel. 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 (newt.ns.cloudflare.com., fiona.ns.cloudflare.com.); DNSSEC enabled; Zone transfers properly restricted.