Blink Charging · Domain Security

Blink Charging Domain Security

Domain security

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

EnergyUnited StatesEV ChargingElectric VehiclesCharging StationsGridDemand ResponseFleet ManagementOCPPOpenADRRoaming

Transport & Host Security

blinkcharging.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Sep 18 05:04:42 2026 GMT
api.blinknetwork.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Feb 13 12:51:03 2027 GMT
host.blinknetwork.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Feb 13 12:51:03 2027 GMT
blinknetwork.com
HTTPS: yes · TLS: TLSv1.2 · HSTS: no · cert expires: Feb 13 12:51:03 2027 GMT
host.blinknetwork.eu
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Oct 13 23:59:59 2026 GMT

Domain (DNS/Email) Security

blinkcharging.com
DNSSEC: no · SPF: yes · DMARC: yes (p=quarantine) · CAA: none
blinknetwork.com
DNSSEC: no · SPF: yes · DMARC: no · CAA: none

Source

Domain Security

blink-charging-domain-security.yml Raw ↑ 
generated: '2026-07-27'
method: probed
source: >-
  0-working/probe-domain-security.py for blinkcharging.com, extended 2026-07-27 with manual
  openssl/dig/curl probes of the blinknetwork.com API + portal hosts, which the script cannot
  reach from apis.yml (no baseURL is recorded for this provider).
hosts:
- host: blinkcharging.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 18 05:04:42 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: api.blinknetwork.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Feb 13 12:51:03 2027 GMT
  hsts: false
  server: kong/2.8.1
  note: Public Kong API gateway. No Strict-Transport-Security header on any response.
- host: host.blinknetwork.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Feb 13 12:51:03 2027 GMT
  hsts: false
  server: AmazonS3
  note: Blink Network host portal (React SPA on S3/CloudFront). No HSTS.
- host: blinknetwork.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Feb 13 12:51:03 2027 GMT
  hsts: false
  server: awselb/2.0
  note: >-
    Apex redirects (301) to host.blinknetwork.com. Negotiates only TLSv1.2 - the weakest TLS of
    any Blink host probed.
- host: host.blinknetwork.eu
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 13 23:59:59 2026 GMT
  hsts: false
  server: AmazonS3
  note: European host portal. Returns 403 on /ocpi/cpo/versions.
domains:
- domain: blinkcharging.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: quarantine
- domain: blinknetwork.com
  dnssec: false
  caa: []
  spf: true
  spf_record: >-
    v=spf1 a mx include:spf.protection.outlook.com include:mail.zendesk.com a:blinknetwork.com
    a:smtp.blinknetwork.com a:dmz.blinknetwork.com ip4:206.225.165.104 ip4:72.44.248.138
    include:amazonses.com +all
  spf_all: +all
  spf_weakness: >-
    The SPF record ends in `+all`, which explicitly passes every sender and so neutralises SPF for
    blinknetwork.com - the domain carrying the API gateway and both host portals.
  dmarc: false
  dmarc_policy: null
findings:
- No CAA record on either registrable domain - any CA may issue for them.
- No DNSSEC on either registrable domain.
- No DMARC record on blinknetwork.com (blinkcharging.com has DMARC at p=quarantine).
- 'SPF on blinknetwork.com ends in +all: a permissive record that authorises all senders.'
- HSTS is present on blinkcharging.com only; no blinknetwork.com host sets it.
- No security.txt on any host (see well-known/blink-charging-well-known.yml).