Jam.gg · Domain Security

Jam Gg Domain Security

Domain security

Domain security posture for Jam.gg, probed live across 1 host(s) and 1 registrable domain(s). Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=none).

CompanyGamingCloud GamingGamesGame DevelopmentEmulationSDKWebRTCFrance

Transport & Host Security

jam.gg
HTTPS: no · HSTS: no

Domain (DNS/Email) Security

jam.gg
DNSSEC: no · SPF: yes · DMARC: yes (p=none) · CAA: none

Source

Domain Security

jam-gg-domain-security.yml Raw ↑ 
generated: '2026-08-17'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: jam.gg
  https: false
domains:
- domain: jam.gg
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: none
x-findings:
  note: >-
    Added by hand on 2026-08-17 alongside the mechanical probe. The probe's boolean fields are
    correct as booleans (a record of each type is present) but both records are malformed in ways
    that make them non-functional, which the booleans cannot express. Recorded here rather than by
    overwriting the probe's output.
  https_false_detail: >-
    `https: false` here is not a missing-redirect finding — the TLS handshake itself never completes.
    jam.gg (Netlify / AWS Global Accelerator, 75.2.70.75 and 99.83.190.102) answers the ClientHello
    with TLS alert 80 (internal_error), the signature of a hostname with no provisioned certificate.
    www.jam.gg (proxy-ssl.webflow.com) answers with TLS alert 40 (handshake_failure). Port 80 on both
    still returns 301 into that dead HTTPS origin, so no client can reach the site at all.
  spf: >-
    RFC 7208 section 3.2 violation — jam.gg publishes TWO v=spf1 TXT records:
    "v=spf1 include:secureserver.net -all" and
    "v=spf1 include:_spf.mailersend.net include:secureserver.net -all".
    More than one SPF record means a checking implementation MUST return permerror, so SPF
    evaluation fails for the domain despite a record being present.
  dmarc: >-
    RFC 7489 violation — the _dmarc.jam.gg TXT record is
    "Value: v=DMARC1; p=none; rua=mailto:jules@jam.gg". The literal "Value: " prefix means the record
    does not begin with the required v=DMARC1 tag, so conforming receivers discard it as not a DMARC
    record. The effective policy is therefore no DMARC at all, not p=none. This looks like a control
    panel form field label pasted into the record value.
  mail: jam.gg MX points at jam-gg.mail.protection.outlook.com (Microsoft 365); registrar/DNS is GoDaddy (domaincontrol.com nameservers).

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/jam-gg-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.

GitHub Google LinkedIn

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