Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
luckyanon.com scored 68/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, DMARC / Email 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 luckyanon.com compares
Grade distribution across 2524 companies we've scanned. luckyanon.com scores better than 37% of them.
79
A+
25
A
183
A-
191
B+
72
B
353
B-
121
C+
116
C
325
C-
118
D+
94
D
241
D-
606
F
luckyanon.com — Grade D+ (68/100)
2524 companies scanned
Security checks
Each check inspects a different part of luckyanon.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.
DMARC / Email Security
Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
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.
DNS Configuration
Strengths: 2 nameservers configured (seth.ns.cloudflare.com., nicole.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
MX Records & Mail Provider
Strengths: Mail handled by in1-smtp.messagingengine.com; 2 MX record(s) configured; Multiple MX records provide redundancy.
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.
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.
security.txt (RFC 9116)
Strengths: security.txt found with 5 field(s); Contact: mailto:[email protected]; Expires in 266 days (2026-12-31T23:59:59.000Z); Disclosure policy: https://luckyanon.com/terms; Canonical URL specified; Preferred languages: en. Issues: Not PGP signed (recommended for authenticity).
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, 69 days remaining; Issued by Google Trust Services; 91 certificates logged in CT; Certificates from 3 CAs: "CLOUDFLARE, Google Trust Services, Let's Encrypt.
Recommended actions
4 items
Steps to improve luckyanon.com's security grade, ranked by impact.
1
Set up email authentication (DKIM)
Without email authentication, anyone can send emails that appear to come from luckyanon.com. This is the most common vector for phishing attacks targeting employees and customers. DKIM is not configured.
Compliance impact
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 recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on luckyanon.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://luckyanon.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for luckyanon.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 luckyanon.com
4
Add optional security headers (CSP, Permissions-Policy)
luckyanon.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://luckyanon.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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=none
Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:spf.messagingengine.com ?all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
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, 69 days remaining; Issued by Google Trust Services; 91 certificates logged in CT; Certificates from 3 CAs: "CLOUDFLARE, Google Trust Services, Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (seth.ns.cloudflare.com., nicole.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.