Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Google Maps
Google Tag Manager
Google Sign-In
Amplitude
Tally
Outgrow
Reddit
Liveramp
Statuspage
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Segment
New Relic
Greenhouse
Active incidents
Fingerprint
LaunchDarkly
Wistia
Twitter
Transcend
Cloudflare Web Analytics
Hotjar
LinkedIn
Influ2
Prismic
Cloudinary
Mapbox
unpkg
Google Search
Adobe Marketo
Demandbase
Qualified
Facebook
StackAdapt
SlideShare
MNTN
IP-API
Vector
Postman
YouTube
Sentry
Certificate Information
Subject
CN=postman.com
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid From
July 16, 2026
Valid Until
October 14, 2026
52 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
19:D5:9E:8B:F7:1E:EF:64:60:8C:9E:FB:AA:7C:FD:8D:DD:C0:DE:90:67:E3:D0:38:D4:F4:6C:84:B8:D0:BA:B3
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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