Overview
Findings
Actions
Details
Related
C+
78 / 100

1degree.org

Security report · Scanned February 18, 2026

Checks
8
Passed
5
Warnings
2
Critical
1
AI-Generated Summary
What this means

1degree.org scored 78/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.

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

How 1degree.org compares

Grade distribution across 2378 companies we've scanned. 1degree.org scores better than 59% of them.

59th percentile
0 Percentile rank 100
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
1degree.org — Grade C+ (78/100) 2378 companies scanned
Security checks

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

DMARC / Email Security
Strengths: DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); No SPF record found.
Problem
DNS Configuration
Strengths: 4 nameservers configured (ns-801.awsdns-36.net., ns-1355.awsdns-41.org., ns-151.awsdns-18.com., ns-1720.awsdns-23.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Needs work
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
Healthy
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Healthy
Certificate Hygiene
Strengths: Certificate valid, 352 days remaining; Issued by Amazon.
Healthy
Recommended actions
3 items

Steps to improve 1degree.org's security grade, ranked by impact.

1
Set up email authentication (SPF)
Impact: 1–2 Days
CRITICAL
Without email authentication, anyone can send emails that appear to come from 1degree.org. This is the most common vector for phishing attacks targeting employees and customers. SPF is not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
2
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for 1degree.org 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 .org TLD
4
Verify: dig +dnssec 1degree.org
3
Add optional security headers (CSP, Permissions-Policy)
Impact: < 1 Hour
LOW
1degree.org has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://1degree.org | 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=none
Strengths: DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 352 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-801.awsdns-36.net., ns-1355.awsdns-41.org., ns-151.awsdns-18.com., ns-1720.awsdns-23.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.