Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
airbnb.com scored 78/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, DMARC / Email Security, 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 airbnb.com compares
Grade distribution across 2378 companies we've scanned. airbnb.com scores better than 59% 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
airbnb.com — Grade C+ (78/100)
2378 companies scanned
Security checks
Each check inspects a different part of airbnb.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 8 nameservers configured (ns-558.awsdns-05.net., dns1.p08.nsone.net., dns2.p08.nsone.net., dns3.p08.nsone.net.); 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
HSTS present but max-age is low (10886400s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, cm, zendesk1, zendesk2, smtpapi).
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 83 days remaining; Issued by DigiCert Inc.
Recommended actions
4 items
Steps to improve airbnb.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for airbnb.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 airbnb.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
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://airbnb.com | grep -i strict
3
Upgrade to TLS 1.3
airbnb.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 airbnb.com:443 -tls1_3
4
Add optional security headers (Referrer-Policy, Permissions-Policy)
airbnb.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://airbnb.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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: google, k1, cm, zendesk1, zendesk2, smtpapi).
SPF Record
Present
v=spf1 include:spf1.airbnb.com ip6:2c0f:fb50:4000::/36 ip6:2a00:1450:4000::/36 ip6:2800:3f0:4000::/3
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (10886400s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 83 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 8 nameservers configured (ns-558.awsdns-05.net., dns1.p08.nsone.net., dns2.p08.nsone.net., dns3.p08.nsone.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.