DNS Gurus
Cached · just now
81/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 23
Algolia logo Algolia Amplitude logo Amplitude AWS logo AWS AWS Certificate Manager logo AWS Certificate Manager Amazon S3 logo Amazon S3 Datadog logo Datadog Forethought logo Forethought Google Analytics logo Google Analytics Google Cloud Storage logo Google Cloud Storage Google Fonts logo Google Fonts Google Search logo Google Search Google Static File Front End logo Google Static File Front End Google Tag Manager logo Google Tag Manager hCaptcha logo hCaptcha Heap logo Heap Lever logo Lever LinkedIn logo LinkedIn Pendo logo Pendo Segment logo Segment Sentry logo Sentry Wistia logo Wistia Zendesk logo Zendesk Google Cloud logo Google Cloud

Certificate Information

Subject
CN=i.prod.lever.co
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
April 13, 2026
Valid Until
October 27, 2026 185 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0D:6B:20:22:B7:5F:66:BB:8A:5C:D2:C1:6F:39:D6:C6:D9:50:51:6E:71:90:09:50:17:B3:F5:D2:FD:1A:92:93
Alternative Names
10 domains

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=15552000; includeSubDomains
Content-Security-Policy
Amazon S3 logo
Basic
default-src; script-src; font-src; +8 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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