Overview
Findings
Actions
Details
Related
F
45 / 100

cuc.ky

Security report · Scanned May 12, 2026

Checks
14
Passed
3
Warnings
6
Critical
0
AI-Generated Summary
What this means

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.

How cuc.ky compares

Grade distribution across 2655 companies we've scanned. cuc.ky scores better than 11% of them.

11th percentile
0 Percentile rank 100
88
A+
27
A
191
A-
198
B+
75
B
371
B-
137
C+
117
C
342
C-
122
D+
95
D
261
D-
631
F
cuc.ky — Grade F (45/100) 2655 companies scanned
Security checks

Each check inspects a different part of cuc.ky's public security setup. Green means healthy, yellow needs attention, red is a problem.

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.
Needs work
DNS CAA Records
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.
Needs work
DMARC / Email Security
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).
Needs work
DNS Configuration
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.
Needs work
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.
Needs work
Certificate Hygiene
Issues: Could not retrieve certificate details.
Needs work
TLS Protocol Support
Could not connect to cuc.ky:443 on any TLS version.
Skipped
TLS Configuration
Could not complete TLS handshake with cuc.ky:443 — [Errno -5] No address associated with hostname
Skipped
HSTS Header
Could not fetch https://cuc.ky — connection failed or timed out.
Skipped
Security Headers
Could not fetch https://cuc.ky — connection failed or timed out.
Skipped
Cookie Security
Could not fetch cuc.ky to analyze cookies: HTTPSConnectionPool(host='cuc.ky', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("HTTPSConnection(host='cuc.ky', port=443): Failed to resolve 'cuc.ky' ([Errno -5] No address associated with hostname)"))
Skipped
MX Records & Mail Provider
Strengths: Mail handled by Mimecast; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Mimecast.
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
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.
Healthy
Recommended actions
1 item

Steps to improve cuc.ky's security grade, ranked by impact.

1
Strengthen email authentication configuration
Impact: 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.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.cuc.ky
2
 
 
●●●
3
 
 
●●●
At a glance

Key data points from the 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.