Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
rescuetime.com scored 72/100, meeting baseline requirements but with 3 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, Security Headers all passed.
4 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 rescuetime.com compares
Grade distribution across 2378 companies we've scanned. rescuetime.com scores better than 47% 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
rescuetime.com — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of rescuetime.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
HSTS Header
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
Certificate Hygiene
Strengths: Certificate valid, 87 days remaining; Issued by Sectigo Limited. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (dns2.rescuetime.com., dns1.rescuetime.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
4 items
Steps to improve rescuetime.com's security grade, ranked by impact.
1
Set up email authentication (DKIM)
Without email authentication, anyone can send emails that appear to come from rescuetime.com. This is the most common vector for phishing attacks targeting employees and customers. DKIM 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
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://rescuetime.com | grep -i strict
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for rescuetime.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 rescuetime.com
4
Review certificate configuration
Certificate issues found for rescuetime.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=none
Strengths: SPF record present with hard-fail (-all). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 a mx include:amazonses.com include:_spf.google.com include:servers.mcsv.net -all
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 87 days remaining; Issued by Sectigo Limited. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (dns2.rescuetime.com., dns1.rescuetime.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.