Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
polleverywhere.com scored 70/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: TLS Configuration, Known Breaches, CVE Exposure 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 polleverywhere.com compares
Grade distribution across 2378 companies we've scanned. polleverywhere.com scores better than 42% 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
polleverywhere.com — Grade C- (70/100)
2378 companies scanned
Security checks
Each check inspects a different part of polleverywhere.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 2/5 security headers present. Missing: X-Content-Type-Options, X-Frame-Options, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DNS Configuration
Strengths: 4 nameservers configured (ns-1766.awsdns-28.co.uk., ns-463.awsdns-57.com., ns-777.awsdns-33.net., ns-1090.awsdns-08.org.); 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: google, s1, s2, k1, zendesk1, zendesk2, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
HSTS Header
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
Certificate Hygiene
Strengths: Certificate valid, 216 days remaining; Issued by Amazon. Issues: 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.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
5 items
Steps to improve polleverywhere.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for polleverywhere.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.polleverywhere.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
Add missing security headers (X-Content-Type-Options, X-Frame-Options, Permissions-Policy)
3 of 5 recommended security headers are missing on polleverywhere.com: X-Content-Type-Options, X-Frame-Options, 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: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://polleverywhere.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for polleverywhere.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 polleverywhere.com
4
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://polleverywhere.com | grep -i strict
5
Review certificate configuration
Certificate issues found for polleverywhere.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_128_GCM_SHA256 (128-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: google, s1, s2, k1, zendesk1, zendesk2, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 a mx include:_spf.google.com include:spf.braintreegateway.com include:mail.zendesk.com includ
Security Headers
2/5 present
Missing: X-Content-Type-Options, X-Frame-Options, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 216 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1766.awsdns-28.co.uk., ns-463.awsdns-57.com., ns-777.awsdns-33.net., ns-1090.awsdns-08.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.