Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
mirror-ai.com scored 68/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers, DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, HSTS Header 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 mirror-ai.com compares
Grade distribution across 2378 companies we've scanned. mirror-ai.com scores better than 38% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
mirror-ai.com — Grade D+ (68/100)
2378 companies scanned
Security checks
Each check inspects a different part of mirror-ai.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
Security Headers
Only 0/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DNS Configuration
Strengths: 4 nameservers configured (ns-736.awsdns-28.net., ns-125.awsdns-15.com., ns-1446.awsdns-52.org., ns-1752.awsdns-27.co.uk.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Certificate Hygiene
Strengths: Issued by Let's Encrypt. Issues: Certificate expires in 27 days — renewal recommended.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
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.
Recommended actions
4 items
Steps to improve mirror-ai.com's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF)
Without email authentication, anyone can send emails that appear to come from mirror-ai.com. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF are 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
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on mirror-ai.com: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://mirror-ai.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for mirror-ai.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 mirror-ai.com
4
Review certificate configuration — expires in 27 days
Certificate issues found for mirror-ai.com: certificate expires in 27 days. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consolidate certificate issuance to 1–2 trusted CAs
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: DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Issued by Let's Encrypt. Issues: Certificate expires in 27 days — renewal recommended.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-736.awsdns-28.net., ns-125.awsdns-15.com., ns-1446.awsdns-52.org., ns-1752.awsdns-27.co.uk.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.