80
verizon.com
Findings
5
·
2
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
verizon.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: TLS Configuration, Known Breaches, CVE Exposure 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.
Action Items
Ordered by priority · 3 items
1
Strengthen email authentication configuration
Email authentication is partially configured for verizon.com but has gaps. Actions needed: add SPF record. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.verizon.com
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 3 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on verizon.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
Remediation Steps
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://verizon.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for verizon.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
Remediation Steps
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 verizon.com
Scan Findings
HSTS Header
Critical
DMARC / Email Security
Warning
DNS Configuration
Warning
TLS Configuration
Healthy
Known Breaches
Healthy
CVE Exposure
Healthy
Security Headers
Healthy
Certificate Hygiene
Healthy