Dow Chemical Domain Security

Domain security

Domain security posture for Dow Inc. (formerly The Dow Chemical Company), probed live across 3 host(s) and 1 registrable domain(s). 3 host(s) serve HTTPS (up to TLSv1.3); 3 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=quarantine).

Materials ScienceChemicalsManufacturingFortune 500Specialty ChemicalsPackagingCoatings

Transport & Host Security

www.dow.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Mar 19 23:59:59 2027 GMT
legal.dow.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Mar 19 23:59:59 2027 GMT
corporate.dow.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Mar 19 23:59:59 2027 GMT

Domain (DNS/Email) Security

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

Source

Domain Security

dow-chemical-domain-security.yml Raw ↑
generated: '2026-09-07'
method: probed
source: >-
  Live DNS/TLS/HTTP probes of every host this record knows: the Website host
  (www.dow.com), the registrable domain, the legal host named in the dow.com footer, and
  the corporate newsroom host. Dow publishes no API baseURL and no OpenAPI, so there are
  no servers[] hosts to probe.
note: >-
  All three subject hosts are one wildcard certificate (CN=*.dow.com, O=Dow Inc.,
  Midland, Michigan) behind Akamai. HSTS IS served — a previous automated pass recorded
  hsts: null because the Akamai edge answers a bare crawler User-Agent with a 403
  interstitial; the header is present on that response and on the origin response alike.
hosts:
  - host: www.dow.com
    https: true
    tls_version: TLSv1.3
    cert_issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1
    cert_subject: CN=*.dow.com, O=Dow Inc., L=Midland, ST=Michigan, C=US
    cert_expires: Mar 19 23:59:59 2027 GMT
    hsts: max-age=15768000 ; includeSubDomains
    hsts_max_age: 15768000
    hsts_include_subdomains: true
    hsts_preload: false
    x_content_type_options: nosniff
    x_frame_options: SAMEORIGIN
    referrer_policy: strict-origin-when-cross-origin
    content_security_policy: null
    edge: akamai
  - host: legal.dow.com
    https: true
    tls_version: TLSv1.3
    cert_subject: CN=*.dow.com, O=Dow Inc., L=Midland, ST=Michigan, C=US
    cert_expires: Mar 19 23:59:59 2027 GMT
    hsts: max-age=15768000 ; includeSubDomains
    edge: akamai
  - host: corporate.dow.com
    https: true
    tls_version: TLSv1.3
    cert_subject: CN=*.dow.com, O=Dow Inc., L=Midland, ST=Michigan, C=US
    cert_expires: Mar 19 23:59:59 2027 GMT
    hsts: max-age=15768000 ; includeSubDomains
    edge: akamai
domains:
  - domain: dow.com
    dnssec: false
    caa: []
    caa_note: No CAA record is published, so any CA may issue for dow.com.
    spf: true
    dmarc: true
    dmarc_policy: quarantine
    dmarc_record: 'v=DMARC1; p=quarantine; rua=mailto:fglsmtp@dow.com'
    dmarc_note: >-
      p=quarantine with an aggregate reporting address, but no p=reject and no ruf.
findings:
  - HSTS is served on every host, includeSubDomains, ~182 days, not preloaded.
  - No CAA record — an absence, and valid data, not an error.
  - DNSSEC is not enabled on dow.com.
  - DMARC is enforced at quarantine rather than reject.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/dow-chemical-domain-security"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.