Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
heydoctor.com scored 75/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, HSTS Header, CVE Exposure 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 heydoctor.com compares
Grade distribution across 2378 companies we've scanned. heydoctor.com scores better than 55% 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
heydoctor.com — Grade C (75/100)
2378 companies scanned
Security checks
Each check inspects a different part of heydoctor.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DNS Configuration
Strengths: 4 nameservers configured (ns-678.awsdns-20.net., ns-1108.awsdns-10.org., ns-1663.awsdns-15.co.uk., ns-432.awsdns-54.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31557600. Missing includeSubDomains. Missing preload directive.
CVE Exposure
Detected technologies: Varnish, Proxy/CDN. (Varnish, 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, 325 days remaining; Issued by GlobalSign nv-sa.
Recommended actions
4 items
Steps to improve heydoctor.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for heydoctor.com 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.heydoctor.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for heydoctor.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 heydoctor.com
3
Upgrade to TLS 1.3
heydoctor.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect heydoctor.com:443 -tls1_3
4
Add optional security headers (X-Frame-Options, Permissions-Policy)
heydoctor.com has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://heydoctor.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net include:amazonses.com ~
Security Headers
3/5 present
Missing: X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31557600. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 325 days remaining; Issued by GlobalSign nv-sa.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-678.awsdns-20.net., ns-1108.awsdns-10.org., ns-1663.awsdns-15.co.uk., ns-432.awsdns-54.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.