Is cuc.ky safe to use as a vendor?

cuc.ky scored 73/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 3 checks passed, 6 warnings, 0 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does cuc.ky use?

TLS configuration for cuc.ky could not be determined. Could not complete TLS handshake with cuc.ky:443 — [Errno -5] No address associated with hostname

Does cuc.ky have SPF configured?

Yes. SPF record found: v=spf1 include:eu._netblocks.mimecast.com include:spf.mailjet.com include:mail.z...

Does cuc.ky have security headers configured?

cuc.ky has 0 of 0 recommended security headers. All recommended headers present.

Does cuc.ky use HSTS?

No. Could not fetch https://cuc.ky — connection failed or timed out.

Has cuc.ky been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does cuc.ky have known CVE vulnerabilities?

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.

Is cuc.ky's SSL certificate valid?

Issues detected. Note: Could not retrieve the live certificate — see the TLS check.

cuc.ky Security Report — Grade C (73/100)

Q: Does cuc.ky have DMARC configured?

Yes. cuc.ky's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 5/10 (within limit); DKIM configured (selectors: k2, k3, mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported.

Q: Does cuc.ky have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-673.awsdns-20.net., ns-1085.awsdns-07.org., ns-1619.awsdns-10.co.uk., ns-448.awsdns-56.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Trust rating

Fair · 73/100

Procurement snapshot

No critical findings. The 5 remaining items are configuration gaps, not architectural problems.

Strengths

MX Records & Mail Provider

Known Breaches

CVE Exposure

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 2–4 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned May 12, 2026

Score

100 75 50 25 0

cuc.ky

73/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

5 items need attention

3 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for cuc.ky is partly set up, but there are gaps: your DMARC policy is set to monitor-only, so nothing actually gets blocked yet. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Change your DMARC policy from "none" to "quarantine" in your DNS settings (you're using Mimecast — see https://www.mimecast.com/content/how-to-set-up-dkim/) — this moves suspicious mail to spam instead of just watching it happen. Your current record with just that change:

v=DMARC1; p=quarantine

2Double-check it's live: search "dmarc record checker" and enter cuc.ky.

Email authentication guide

Report unlocked.

View all 3 passed checks

MX Records & Mail Provider

Known Breaches

CVE Exposure

Couldn't check: TLS Protocol Support, TLS Configuration, HSTS Header, Security Headers, Cookie Security, Certificate Hygiene — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so these aren't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded C

699 companies · LynxRadar ranking

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 5/10 (within limit); DKIM configured (selectors: k2, k3, mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

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.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-673.awsdns-20.net., ns-1085.awsdns-07.org., ns-1619.awsdns-10.co.uk., ns-448.awsdns-56.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

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.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

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.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

Could not load cuc.ky's homepage to detect its e-commerce platform, payment processor, or CDN.