Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
up.codes scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, TLS Configuration, Known Breaches all passed.
1 action item 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 up.codes compares
Grade distribution across 2378 companies we've scanned. up.codes scores better than 96% 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
up.codes — Grade A (95/100)
2378 companies scanned
Security checks
Each check inspects a different part of up.codes's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
DNS Configuration
Strengths: 4 nameservers configured (ns-2038.awsdns-62.co.uk., ns-594.awsdns-10.net., ns-62.awsdns-07.com., ns-1427.awsdns-50.org.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2).
CVE Exposure
Detected technologies: Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 143 days remaining; Issued by Amazon.
Recommended actions
1 item
Steps to improve up.codes's security grade, ranked by impact.
1
Add optional security headers (Referrer-Policy, Permissions-Policy)
up.codes has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://up.codes | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:19523768.spf07.hubspotemail.net include:email.chargebee.com include:_spf.google.com -
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 143 days remaining; Issued by Amazon.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-2038.awsdns-62.co.uk., ns-594.awsdns-10.net., ns-62.awsdns-07.com., ns-1427.awsdns-50.org.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.