Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
uns.com scored 78/100, meeting baseline requirements but with 9 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: DMARC / Email Security, Cookie Security, HSTS Header all passed.
4 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 uns.com compares
Grade distribution across 2655 companies we've scanned. uns.com scores better than 59% of them.
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
uns.com — Grade C+ (78/100)
2655 companies scanned
Security checks
Each check inspects a different part of uns.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
MX Records & Mail Provider
Strengths: Mail handled by Microsoft 365; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
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
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.
DNS Configuration
Strengths: 2 nameservers configured (neil.ns.cloudflare.com., kiki.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
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, 86 days remaining; Issued by DigiCert Inc; 482 certificates logged in CT. Issues: Certificates issued by 9 different CAs (threshold: 8 for 482 logged certs) — possible misconfiguration or shadow IT.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2, cm).
HSTS Header
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
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.
CVE Exposure
Detected technologies: cloudflare, WP Engine. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
1 item
Steps to improve uns.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for uns.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 uns.com
See all 3 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
3
4
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2, cm).
SPF Record
Present
v=spf1 include:_spf.createsend.com include:_u.uns.com._spf.smart.ondmarc.com -all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 86 days remaining; Issued by DigiCert Inc; 482 certificates logged in CT. Issues: Certificates issued by 9 different CAs (threshold: 8 for 482 logged certs) — possible misconfiguration or shadow IT.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (neil.ns.cloudflare.com., kiki.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.