Overview
Findings
Actions
Details
Related
D+
68 / 100

rejuvenationtech.com

Security report · Scanned February 18, 2026

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

rejuvenationtech.com scored 68/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.

Critical gaps in: HSTS Header, Security Headers. Positive signals: Known Breaches, TLS Configuration, DNS Configuration 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 rejuvenationtech.com compares

Grade distribution across 2378 companies we've scanned. rejuvenationtech.com scores better than 38% of them.

38th 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
rejuvenationtech.com — Grade D+ (68/100) 2378 companies scanned
Security checks

Each check inspects a different part of rejuvenationtech.com'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.
Problem
Security Headers
Only 1/5 security headers present. Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
CVE Exposure
Detected technologies: cloudflare, PHP/8.2.29. (cloudflare detected but excluded from CVE matching — upstream infrastructure). 2 medium-severity CVE(s) found. Review recommended.
Needs work
Certificate Hygiene
Strengths: Certificate valid, 80 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
DNS Configuration
Strengths: 2 nameservers configured (journey.ns.cloudflare.com., oswald.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2).
Healthy
Recommended actions
4 items

Steps to improve rejuvenationtech.com's security grade, ranked by impact.

1
Enable HSTS (HTTP Strict Transport Security)
Impact: < 1 Hour
HIGH
The HSTS header is missing on rejuvenationtech.com. 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://rejuvenationtech.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
2
Add missing security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
4 of 5 recommended security headers are missing on rejuvenationtech.com: 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: X-Content-Type-Options: nosniff
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://rejuvenationtech.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review potential CVE exposure in detected software
Impact: 2–4 Hours
MEDIUM
Software detected on rejuvenationtech.com has potential CVE matches. Review the specific CVEs and confirm whether the installed version is affected.
How to fix this
1
Review matched CVEs and confirm installed versions
2
Update software if vulnerable versions are confirmed
3
Consider hiding version information in server headers
4
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for rejuvenationtech.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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2).
SPF Record
Present
v=spf1 include:spf.protection.outlook.com -all
Security Headers
1/5 present
Missing: 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: Certificate valid, 80 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (journey.ns.cloudflare.com., oswald.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.