Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
app.cymulate.com scored 78/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
3 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 app.cymulate.com compares
Grade distribution across 2378 companies we've scanned. app.cymulate.com scores better than 59% 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
app.cymulate.com — Grade C+ (78/100)
2378 companies scanned
Security checks
Each check inspects a different part of app.cymulate.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with hard-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).
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 (12 record(s)); Authorized CAs: amazon.com, amazonaws.com, amazontrust.com, awstrust.com, letsencrypt.org. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Strengths: DNSSEC enabled. Issues: No NS records found (unusual).
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.
Certificate Hygiene
Strengths: Certificate valid, 81 days remaining; Issued by Google Trust Services; 156 certificates logged in CT. Issues: Certificates issued by 7 different CAs (threshold: 5 for 156 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
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.
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.
Known Breaches
No known breaches found in public disclosure databases.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
HSTS Header
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: cloudflare, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
3 items
Steps to improve app.cymulate.com'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 app.cymulate.com. 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 app.cymulate.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 app.cymulate.com
3
Review certificate configuration
Certificate issues found for app.cymulate.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
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: SPF record present with hard-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 ip4:168.245.119.24 include:spf.protection.outlook.com include:mail.zendesk.com include:_spf.s
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 81 days remaining; Issued by Google Trust Services; 156 certificates logged in CT. Issues: Certificates issued by 7 different CAs (threshold: 5 for 156 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: DNSSEC enabled. Issues: No NS records found (unusual).