Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
m.me 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: DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
5 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 m.me compares
Grade distribution across 2378 companies we've scanned. m.me 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
m.me — Grade D+ (68/100)
2378 companies scanned
Security checks
Each check inspects a different part of m.me's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
DNS Configuration
Strengths: 4 nameservers configured (b.ns.facebook.com., d.ns.facebook.com., c.ns.facebook.com., a.ns.facebook.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Referrer-Policy.
Certificate Hygiene
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical; Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_CHACHA20_POLY1305_SHA256 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
5 items
Steps to improve m.me's security grade, ranked by impact.
1
Set up email authentication (DMARC, DKIM)
Without email authentication, anyone can send emails that appear to come from m.me. This is the most common vector for phishing attacks targeting employees and customers. DMARC, DKIM 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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for m.me 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 .me TLD
4
Verify: dig +dnssec m.me
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://m.me | grep -i strict
4
Review certificate configuration — expires in 7 days
Certificate issues found for m.me: certificate expires in 7 days; wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. 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
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
5
Add optional security headers (X-Frame-Options, Referrer-Policy)
m.me has most security headers configured. Missing: X-Frame-Options, Referrer-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Verify with: curl -sI https://m.me | 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_CHACHA20_POLY1305_SHA256 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 a ~all
Security Headers
3/5 present
Missing: X-Frame-Options, Referrer-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 7 days — critical; Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (b.ns.facebook.com., d.ns.facebook.com., c.ns.facebook.com., a.ns.facebook.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.