Allotex · Domain Security

Allotex Domain Security

Domain security

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

CompanyMedical DevicesOphthalmologyBiologicsvision-correctioncorneal-allograftPresbyopiahyperopiarefractive-surgerytissue-processingLife SciencesClinical Trialscontent-api

Transport & Host Security

us.allotex.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Oct 22 21:19:24 2026 GMT
allotex.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Oct 22 21:19:24 2026 GMT

Domain (DNS/Email) Security

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

Source

Domain Security

Raw ↑ 
generated: '2026-08-06'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
note: >-
  Scoped to hosts Allotex controls. The mechanical probe also resolved developer.wordpress.org /
  wordpress.org because the Content API humanURL points at the upstream WordPress REST handbook;
  those are not Allotex infrastructure and have been removed. Both Allotex hosts are the same
  WordPress multisite install, served from Kinsta behind Cloudflare (observed response headers:
  server: cloudflare, ki-edge, x-kinsta-cache).
hosts:
- host: us.allotex.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 22 21:19:24 2026 GMT
  hsts: false
- host: allotex.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 22 21:19:24 2026 GMT
  hsts: false
domains:
- domain: allotex.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: none
findings:
- id: no-hsts
  severity: low
  detail: >-
    Neither us.allotex.com nor allotex.com returns a Strict-Transport-Security header, so a first
    request over http is not protected against downgrade.
- id: no-caa
  severity: informational
  detail: >-
    allotex.com publishes no CAA record, so any public CA may issue for the domain.
- id: no-dnssec
  severity: informational
  detail: allotex.com is not DNSSEC-signed.
- id: dmarc-policy-none
  severity: low
  detail: >-
    allotex.com publishes SPF and a DMARC record, but the DMARC policy is p=none - failures are
    reported, not rejected or quarantined.
- id: x-content-type-options-present
  severity: informational
  detail: >-
    The REST API responses do carry x-content-type-options: nosniff and x-robots-tag: noindex.

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/allotex-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 email required.

GitHub Google LinkedIn

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