Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
Adobe Fonts (Typekit)
AWS
Active incidents
Amazon S3
BootstrapCDN
Braintree
Branch
Facebook
GoDaddy
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
Heroku
Intercom
JW Player
Mixpanel
Sentry
TrackJS
Twitter
Vimeo
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=*.vidmob.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
April 23, 2026
Valid Until
November 07, 2026
165 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
20:18:F7:FE:AF:90:13:BA:49:F5:11:B0:0D:19:40:A0:F6:AE:66:9B:0B:7D:B0:DA:44:13:03:51:EF:03:8F:60
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=2592000; includeSubDomains
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
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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