Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
govpredict.com scored 75/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: DNS Configuration, Known Breaches, DMARC / Email Security all passed.
3 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 govpredict.com compares
Grade distribution across 2378 companies we've scanned. govpredict.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
govpredict.com — Grade C (75/100)
2378 companies scanned
Security checks
Each check inspects a different part of govpredict.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
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.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
Certificate Hygiene
Strengths: Certificate valid, 300 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 4 nameservers configured (ns-622.awsdns-13.net., ns-1509.awsdns-60.org., ns-162.awsdns-20.com., ns-1706.awsdns-21.co.uk.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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, mandrill, cm, smtpapi).
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
3 items
Steps to improve govpredict.com's security grade, ranked by impact.
1
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 govpredict.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://govpredict.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Upgrade to TLS 1.3
govpredict.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 govpredict.com:443 -tls1_3
3
Review certificate configuration
Certificate issues found for govpredict.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.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, mandrill, cm, smtpapi).
SPF Record
Present
v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:customeriomail.com include:661276
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 300 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-622.awsdns-13.net., ns-1509.awsdns-60.org., ns-162.awsdns-20.com., ns-1706.awsdns-21.co.uk.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.