Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
predxionbio.com scored 60/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DNS Configuration, HSTS Header, Security Headers. Positive signals: Known Breaches, TLS Configuration, Certificate Hygiene all passed.
5 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 predxionbio.com compares
Grade distribution across 2378 companies we've scanned. predxionbio.com scores better than 25% 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
predxionbio.com — Grade D- (60/100)
2378 companies scanned
Security checks
Each check inspects a different part of predxionbio.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (ns01.f123jp9953.info., ns02.f123jp9953.info.); 1 MX records present. Issues: DNSSEC not configured — DNS responses can be spoofed; Zone transfer (AXFR) allowed on: ns01.f123jp9953.info., ns02.f123jp9953.info. — full zone data exposed.
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.66, PHP/7.4.33. 3 high-severity CVE(s) found (CVSS 7.0–8.9): CVE-2025-55753, CVE-2025-59775, CVE-2025-58098. Patching recommended.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
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.
Certificate Hygiene
Strengths: Certificate valid, 32 days remaining; Issued by Let's Encrypt.
Recommended actions
5 items
Steps to improve predxionbio.com's security grade, ranked by impact.
1
Fix DNS security vulnerabilities — zone transfer exposed
Zone transfer (AXFR) is allowed on nameservers for predxionbio.com, exposing your full DNS zone data to attackers. Critical DNS configuration issues were found that require immediate attention.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution
SOC 2CC6.1
Network security controls
How to fix this
1
Restrict zone transfers to authorized secondary nameservers only
2
Enable DNSSEC signing
3
Ensure at least 2 geographically distributed nameservers
4
Verify zone transfers are blocked: dig AXFR predxionbio.com @ns1
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 HSTS (HTTP Strict Transport Security)
The HSTS header is missing on predxionbio.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://predxionbio.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
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 predxionbio.com: 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://predxionbio.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Strengthen email authentication configuration
Email authentication is partially configured for predxionbio.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.predxionbio.com
5
Review potential CVE exposure in detected software
Software detected on predxionbio.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
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 soft-fail (~all); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 +a +mx +ip4:133.242.134.69 ~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
Valid
Strengths: Certificate valid, 32 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns01.f123jp9953.info., ns02.f123jp9953.info.); 1 MX records present. Issues: DNSSEC not configured — DNS responses can be spoofed; Zone transfer (AXFR) allowed on: ns01.f123jp9953.info., ns02.f123jp9953.info. — full zone data exposed.