Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
hunter2.com scored 60/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, CVE Exposure, Certificate Hygiene 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 hunter2.com compares
Grade distribution across 2378 companies we've scanned. hunter2.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
hunter2.com — Grade D- (60/100)
2378 companies scanned
Security checks
Each check inspects a different part of hunter2.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
DNS Configuration
Strengths: 4 nameservers configured (ns-587.awsdns-09.net., ns-1449.awsdns-53.org., ns-1832.awsdns-37.co.uk., ns-381.awsdns-47.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
HSTS Header
Could not fetch https://hunter2.com — connection failed or timed out.
Security Headers
Could not fetch https://hunter2.com — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 393 days remaining; Issued by Amazon.
Recommended actions
3 items
Steps to improve hunter2.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for hunter2.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.hunter2.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for hunter2.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 hunter2.com
3
Upgrade to TLS 1.3
hunter2.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 hunter2.com:443 -tls1_3
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:mailgun.org include:_spf.google.com ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://hunter2.com — connection failed or timed out.
SSL Certificate
Valid
Strengths: Certificate valid, 393 days remaining; Issued by Amazon.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-587.awsdns-09.net., ns-1449.awsdns-53.org., ns-1832.awsdns-37.co.uk., ns-381.awsdns-47.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.