Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
themednet.org scored 57/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Critical gaps in: HSTS Header, Security Headers, CVE Exposure. Positive signals: TLS Configuration, Known Breaches, DMARC / Email Security all passed.
5 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 themednet.org compares
Grade distribution across 2378 companies we've scanned. themednet.org scores better than 19% 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
themednet.org — Grade F (57/100)
2378 companies scanned
Security checks
Each check inspects a different part of themednet.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
Only 0/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
CVE Exposure
Detected technologies: Apache/2.4.54, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). 1 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2022-36760. Immediate patching recommended.
DNS Configuration
Strengths: 4 nameservers configured (ns-1525.awsdns-62.org., ns-1984.awsdns-56.co.uk., ns-241.awsdns-30.com., ns-771.awsdns-32.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Certificate Hygiene
Strengths: Issued by Amazon. Issues: Certificate expires in 28 days — renewal recommended; Wildcard certificate in use — broader attack surface if compromised.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2, k1, mandrill).
Recommended actions
5 items
Steps to improve themednet.org's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on themednet.org. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://themednet.org | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on themednet.org: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://themednet.org | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Patch 1 critical CVE
Externally visible software on themednet.org has 1 critical CVE (CVSS >= 9.0). Update the affected software to the latest patched version.
Compliance impact
NIST 800-53SI-2
Flaw remediation
PCI-DSS 4.0Req 6.3.3
Critical patches within 1 month
How to fix this
1
Review CVEs: CVE-2022-36760
2
Update affected software to latest patched versions
3
Verify patches applied: re-scan after update
4
Consider hiding server version headers to reduce future exposure
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for themednet.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 themednet.org
5
Review certificate configuration — expires in 28 days
Certificate issues found for themednet.org: certificate expires in 28 days; wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
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_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, k1, mandrill).
SPF Record
Present
v=spf1 include:spf.mandrillapp.com include:_spf.google.com -all
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Issues
Strengths: Issued by Amazon. Issues: Certificate expires in 28 days — renewal recommended; Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1525.awsdns-62.org., ns-1984.awsdns-56.co.uk., ns-241.awsdns-30.com., ns-771.awsdns-32.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.