DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 4
AWS logo AWS Active incidents AWS Certificate Manager logo AWS Certificate Manager Bugsnag logo Bugsnag Google Fonts logo Google Fonts

Certificate Information

Subject
CN=merchant.pba.mastercard.com.au
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
August 18, 2026
Valid Until
March 03, 2027 145 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FD:D1:AF:2C:31:DE:A2:84:D8:50:46:E2:D9:D0:0A:28:DA:E5:68:D7:88:7C:9E:D0:F9:ED:41:41:A5:C6:BC:2F
Alternative Names
3 domains

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=10368000; includeSubdomains; preload
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Google Fonts logo
Good
default-src; img-src; script-src; +5 more Analyze
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
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