Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Florida, L=Fort Lauderdale, O=Cloud Software Group, Inc., CN=uberagent.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
September 25, 2025
Valid Until
September 24, 2026 243 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F6:BA:10:DC:03:ED:62:83:F2:0B:F2:EB:49:18:E8:0F:C3:16:05:D1:B2:E6:BB:84:D8:C0:A1:9B:16:40:9D:AA
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31449600
Content-Security-Policy
Weak
frame-ancestors; object-src; plugin-types
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=(), microphone=(), camera=(), usb=(), midi=(), payment=(), fullscreen=(self), autoplay=(self), accelerometer=(), gyroscope=(), magnetometer=(), ambient-light-sensor=(), clipboard-read=(), clipboard-write=(self)
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives

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