Is cuc.ky safe to use as a vendor?

cuc.ky scored 45/100 on LynxRadar's security posture assessment. The domain has significant security gaps that should be addressed. 3 checks passed, 6 warnings, 0 critical issues across 14 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 security headers configured?

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

Is cuc.ky's SSL certificate valid?

Issues detected. Issues: Could not retrieve certificate details.

cuc.ky Security Report — Grade F (45/100)

Q: Does cuc.ky have DMARC configured?

Yes. cuc.ky's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).

Q: Does cuc.ky use HSTS?

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

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.

45/100

cuc.ky

May 12, 2026 ·

1+ Warnings 3 Passed

AI Summary

cuc.ky scored 45/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.

Positive signals: MX Records & Mail Provider, Known Breaches, CVE Exposure all passed.

3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

Better than 11% of 2681 companies scanned.

011th pct100

A+

A-

B+

B-

C+

C-

D+

D-

MTA-STS & TLS Reporting

DNS CAA Records

DMARC / Email Security

DNS Configuration

security.txt (RFC 9116)

Certificate Hygiene

TLS Protocol Support

TLS Configuration

HSTS Header

Security Headers

Cookie Security

MX Records & Mail Provider

Known Breaches

CVE Exposure

cuc.ky

45/100

No critical issues — great work!

Strengthen email authentication configuration

2–4 hours High

Email authentication is partially configured for cuc.ky but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)

2Verify with: nslookup -type=txt _dmarc.cuc.ky

2 items locked

Unlock the full action plan

Report unlocked.

At a glance

Full data from this scan

TLS Version

Issues detected

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

DMARC Policy

p=none

Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).

SPF Record

Present

v=spf1 include:eu._netblocks.mimecast.com include:spf.mailjet.com include:mail.zendesk.com include:s

Security Headers

0/0 present

All headers configured.

HSTS

Not enabled

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

SSL Certificate

Issues

Issues: Could not retrieve certificate details.

DNSSEC

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.

Similar companies

Other domains with comparable security profiles.