Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
swiftype.com scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
4 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 swiftype.com compares
Grade distribution across 2378 companies we've scanned. swiftype.com scores better than 64% 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
swiftype.com — Grade B- (80/100)
2378 companies scanned
Security checks
Each check inspects a different part of swiftype.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, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
DNS Configuration
Strengths: 4 nameservers configured (ns-1799.awsdns-32.co.uk., ns-610.awsdns-12.net., ns-140.awsdns-17.com., ns-1478.awsdns-56.org.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 119 days remaining; Issued by DigiCert Inc. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Recommended actions
4 items
Steps to improve swiftype.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for swiftype.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.swiftype.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 swiftype.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 swiftype.com
3
Add optional security headers (CSP, Permissions-Policy)
swiftype.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://swiftype.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Review certificate configuration
Certificate issues found for swiftype.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.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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:helpscoutemail.com include:mktomail.com include:_spf.salesforce.com include:_netblock
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 119 days remaining; Issued by DigiCert Inc. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1799.awsdns-32.co.uk., ns-610.awsdns-12.net., ns-140.awsdns-17.com., ns-1478.awsdns-56.org.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.