Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Apple ID
PayPal
Adobe Fonts (Typekit)
AMP
Arkose Labs
Microsoft Advertising
Branch
DigiCert
Facebook
GeeTest
Google AdSense
Google Analytics
Google Cloud Storage
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Maps
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Google Sign-In
Google Tag Manager
Mapbox
New Relic
Plaid
Stripe
Yahoo
Google Cloud
Certificate Information
Subject
C=US, ST=California, L=San Francisco, O=Airbnb, Inc., CN=global.airbnb-web.next.certs.akamai.airbnb.net
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1
Valid From
February 23, 2026
Valid Until
February 22, 2027
209 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
A0:51:FD:B1:B5:00:3F:CE:C9:0C:C7:08:1A:03:FE:1E:BE:4B:09:53:58:30:24:A3:FF:11:12:18:1C:09:49:58
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=10886400; includeSubdomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports
Subject Alternative Names
61 domains
next.airbnb.com
ar.next.airbnb.com
az.next.airbnb.com
bg.next.airbnb.com
bs.next.airbnb.com
ca.next.airbnb.com
cnr.next.airbnb.com
cs.next.airbnb.com
da.next.airbnb.com
de.next.airbnb.com
el.next.airbnb.com
es-l.next.airbnb.com
es.next.airbnb.com
et.next.airbnb.com
fi.next.airbnb.com
fr.next.airbnb.com
ga.next.airbnb.com
he.next.airbnb.com
hi.next.airbnb.com
hr.next.airbnb.com
hu.next.airbnb.com
hy.next.airbnb.com
id.next.airbnb.com
is.next.airbnb.com
it.next.airbnb.com
ja.next.airbnb.com
ka.next.airbnb.com
kn.next.airbnb.com
ko.next.airbnb.com
lt.next.airbnb.com
lv.next.airbnb.com
mk.next.airbnb.com
mr.next.airbnb.com
ms.next.airbnb.com
mt.next.airbnb.com
nl.next.airbnb.com
no.next.airbnb.com
pl.next.airbnb.com
pt.next.airbnb.com
ro.next.airbnb.com
ru.next.airbnb.com
sk.next.airbnb.com
sl.next.airbnb.com
sq.next.airbnb.com
sr.next.airbnb.com
sv.next.airbnb.com
sw.next.airbnb.com
th.next.airbnb.com
tl.next.airbnb.com
tr.next.airbnb.com
uk.next.airbnb.com
vi.next.airbnb.com
xh.next.airbnb.com
xx.next.airbnb.com
xxkey.next.airbnb.com
xxlong.next.airbnb.com
xxrtl.next.airbnb.com
zh-t.next.airbnb.com
zh.next.airbnb.com
zu.next.airbnb.com
global.airbnb-web.next.certs.akamai.airbnb.net
Other domains in certificate