Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
avo.app scored 98/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, Known Breaches, HSTS Header all passed.
1 action item 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 avo.app compares
Grade distribution across 2598 companies we've scanned. avo.app scores better than 97% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
avo.app — Grade A+ (98/100)
2598 companies scanned
Security checks
Each check inspects a different part of avo.app's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (ns33.domaincontrol.com., ns34.domaincontrol.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31556926 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2).
CVE Exposure
Detected technologies: Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services.
Recommended actions
1 item
Steps to improve avo.app's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for avo.app 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 .app TLD
4
Verify: dig +dnssec avo.app
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:sendgrid.net include:_spf.google.com include:4429343.spf08.hubspotemail.net include:s
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=31556926 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns33.domaincontrol.com., ns34.domaincontrol.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.