Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
asendia.ai scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: DMARC / Email Security, TLS Configuration, Known Breaches 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 asendia.ai compares
Grade distribution across 2394 companies we've scanned. asendia.ai scores better than 81% of them.
72
A+
22
A
180
A-
182
B+
69
B
335
B-
114
C+
111
C
301
C-
110
D+
92
D
217
D-
589
F
asendia.ai — Grade B+ (88/100)
2394 companies scanned
Security checks
Each check inspects a different part of asendia.ai's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 2 nameservers configured (violet.ns.cloudflare.com., stanley.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google).
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.
Security Headers
4/5 security headers present. Missing: CSP.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
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.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Certificate Hygiene
Strengths: Certificate valid, 86 days remaining; Issued by DigiCert Inc; 176 certificates logged in CT; Certificates from 5 CAs: "DigiCert, DigiCert Inc, Google Trust Services.
Recommended actions
2 items
Steps to improve asendia.ai's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on asendia.ai. 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
How to fix this
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://asendia.ai | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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 asendia.ai 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 .ai TLD
4
Verify: dig +dnssec asendia.ai
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com include:spf.mailjet.com ~all
Security Headers
4/5 present
Missing: CSP
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 86 days remaining; Issued by DigiCert Inc; 176 certificates logged in CT; Certificates from 5 CAs: "DigiCert, DigiCert Inc, Google Trust Services.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (violet.ns.cloudflare.com., stanley.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.