Allo-Media · Domain Security

Allo Media Domain Security

Domain security

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

CompanyAi DataSpeech RecognitionSpeech-to-TextConversation IntelligenceCall TrackingVoice AINatural Language ProcessingCall AnalyticsContact CenterSpeech AnalyticsTranscriptionFrance

Transport & Host Security

uh.live

HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Nov 15 09:34:08 2026 GMT

docs.allo-media.net

HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Oct 6 16:59:19 2026 GMT

activate.uh.live

HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 15 09:34:08 2026 GMT

Domain (DNS/Email) Security

uh.live

DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: yes

allo-media.net

DNSSEC: yes · SPF: yes · DMARC: no · CAA: yes

Source

Domain Security

generated: '2026-08-17'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
note: >-
  Probed 2026-08-17. Findings worth reading rather than just recording:
  TLS 1.3 on all three reachable hosts with valid certs. HSTS is enabled on the
  marketing host uh.live (max-age 16,000,000 ~ 185 days) but NOT on the API host
  activate.uh.live or the docs host — the inverse of the priority you would want,
  since the API host is where bearer tokens travel.
  The two registrable domains are managed to different standards: allo-media.net
  has DNSSEC enabled but NO DMARC record, while uh.live has DMARC at p=reject
  (strong) but no DNSSEC. Each domain has the control the other is missing, which
  is the signature of a rebrand where DNS hygiene was rebuilt rather than
  carried across. Both publish SPF and both publish CAA (uh.live pins Let's
  Encrypt, DigiCert and Comodo; allo-media.net pins the same three including
  wildcards).
  Reachability caveat: api.uh.live and hermes.allo-media.net could not be probed
  in this pass because the provider's edge intermittently refuses connections
  from a single source IP after a short burst; their absence below is our
  limitation, not a provider defect.
hosts:
- host: uh.live
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov 15 09:34:08 2026 GMT
  hsts: true
  hsts_max_age: 16000000
- host: docs.allo-media.net
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  6 16:59:19 2026 GMT
  hsts: false
- host: activate.uh.live
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov 15 09:34:08 2026 GMT
  hsts: false
domains:
- domain: uh.live
  dnssec: false
  caa:
  - 0 issue "letsencrypt.org"
  - 0 issue "digicert.com"
  - 0 issue "comodoca.com"
  spf: true
  dmarc: true
  dmarc_policy: reject
- domain: allo-media.net
  dnssec: true
  caa:
  - 0 issue "comodoca.com"
  - 0 issuewild "comodoca.com"
  - 0 issue "digicert.com"
  - 0 issuewild "digicert.com"
  - 0 issuewild "letsencrypt.org"
  - 0 issue "letsencrypt.org"
  spf: true
  dmarc: false

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/allo-media-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.