Autopay · Domain Security

Autopay Domain Security

Domain security

Domain security posture for Autopay, probed live across 3 host(s) and 2 registrable domain(s). 2 host(s) serve HTTPS (up to TLSv1.3); 1 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=reject).

ParkingParking PaymentsFleet ManagementPermitsParking OperatorsNorway

Transport & Host Security

developer.autopay.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Aug 13 12:37:23 2026 GMT
autopay.no
HTTPS: no · HSTS: no
api.autopay.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Sep 8 09:39:44 2026 GMT

Domain (DNS/Email) Security

autopay.io
DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: yes
autopay.no
DNSSEC: yes · SPF: yes · DMARC: yes (p=reject) · CAA: none

Source

Domain Security

autopay-domain-security.yml Raw ↑ 
generated: '2026-07-11'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: developer.autopay.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Aug 13 12:37:23 2026 GMT
  hsts: true
  hsts_max_age: 31556926
- host: autopay.no
  https: false
- host: api.autopay.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep  8 09:39:44 2026 GMT
  hsts: null
domains:
- domain: autopay.io
  dnssec: false
  caa:
  - 0 issue "pki.goog"
  - 0 issuewild ";"
  - 0 issue "letsencrypt.org"
  - 0 iodef "mailto:security@autopay.io"
  spf: true
  dmarc: true
  dmarc_policy: reject
- domain: autopay.no
  dnssec: true
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: reject