Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
helloverify.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DMARC / Email Security, DNS Configuration all passed.
2 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 helloverify.com compares
Grade distribution across 2378 companies we've scanned. helloverify.com scores better than 78% 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
helloverify.com — Grade B (85/100)
2378 companies scanned
Security checks
Each check inspects a different part of helloverify.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
Certificate Hygiene
Strengths: Certificate valid, 225 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (ns60.domaincontrol.com., ns59.domaincontrol.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
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.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, s1, s2). Issues: DMARC has no aggregate report URI (rua).
Recommended actions
2 items
Steps to improve helloverify.com's security grade, ranked by impact.
1
Upgrade to TLS 1.3
helloverify.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 helloverify.com:443 -tls1_3
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for helloverify.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: selector1, s1, s2). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 include:spf.protection.outlook.com -all
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 225 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (ns60.domaincontrol.com., ns59.domaincontrol.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.