Neo4j · Domain Security

Neo4J Domain Security

Domain security

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

Graph DatabaseCypherCloudGraphQLDriversAPIs

Transport & Host Security

neo4j.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Sep 10 16:44:37 2026 GMT
api.neo4j.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 21 08:03:04 2026 GMT

Domain (DNS/Email) Security

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

Source

Domain Security

Raw ↑ 
generated: '2026-07-11'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: neo4j.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 10 16:44:37 2026 GMT
  hsts: true
  hsts_max_age: 63072000
- host: api.neo4j.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov 21 08:03:04 2026 GMT
  hsts: null
domains:
- domain: neo4j.com
  dnssec: true
  caa:
  - 0 issue "pki.goog; cansignhttpexchanges=yes"
  - 0 issue "sectigo.com"
  - 0 issue "ssl.com"
  - 0 issue "starfieldtech.com"
  - 0 issuewild "comodoca.com"
  - 0 issuewild "digicert.com; cansignhttpexchanges=yes"
  spf: true
  dmarc: true
  dmarc_policy: reject
- domain: neo4j.io
  dnssec: false
  caa: []
  spf: false
  dmarc: false