Wyndham Hotels & Resorts · Domain Security

Wyndham Hotels Domain Security

Domain security

Domain security posture for Wyndham Hotels & Resorts, probed live across 8 host(s) and 2 registrable domain(s). 8 host(s) serve HTTPS (up to TLSv1.2); 4 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=reject).

TravelUnited StatesHospitalityHotelsBookingFranchisingDistributionLoyaltyGDS

Transport & Host Security

www.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.2 · HSTS: yes · cert expires: Jan 24 23:59:59 2027 GMT
corporate.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Sep 13 15:40:32 2026 GMT
development.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Sep 13 22:56:31 2026 GMT
investor.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 12 08:02:03 2026 GMT
mcp.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Dec 10 23:59:59 2026 GMT
aisearch.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Dec 10 23:59:59 2026 GMT
connect.wyndhamhotels.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 19 03:31:55 2026 GMT
www.wyndhambusiness.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Oct 18 21:51:59 2026 GMT

Domain (DNS/Email) Security

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

Source

Domain Security

wyndham-hotels-domain-security.yml Raw ↑
generated: '2026-07-28'
method: probed
source: live DNS/TLS/HTTP probes of every Wyndham host named in apis.yml, review.yml
  and the harvested discovery documents
hosts:
- host: www.wyndhamhotels.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Jan 24 23:59:59 2027 GMT
  hsts: true
  hsts_max_age: 31536000
  edge: Akamai
- host: corporate.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 13 15:40:32 2026 GMT
  hsts: false
- host: development.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 13 22:56:31 2026 GMT
  hsts: false
  note: WordPress on WP Engine; anonymous WordPress REST API and a gated MCP adapter.
- host: investor.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 12 08:02:03 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: mcp.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Dec 10 23:59:59 2026 GMT
  hsts: null
  note: Provisioned behind Akamai; every path returns 503 with no HSTS header.
- host: aisearch.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Dec 10 23:59:59 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: connect.wyndhamhotels.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 19 03:31:55 2026 GMT
  hsts: true
  hsts_max_age: 31536000
  note: Returns HTTP 204 with an empty body on every path.
- host: www.wyndhambusiness.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 18 21:51:59 2026 GMT
  hsts: false
  edge: Cloudflare (WP Engine origin)
  note: |
    Carries the only live, machine-readable API surfaces on the estate — an
    anonymous WordPress REST API and an OAuth 2.1 protected MCP server — and is one
    of the hosts with no HSTS.
domains:
- domain: wyndhamhotels.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: reject
- domain: wyndhambusiness.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: quarantine
findings:
  no_caa: |
    Neither registrable domain publishes a CAA record, so no certificate authority is
    pinned for either estate.
  no_dnssec: Neither domain is DNSSEC-signed.
  hsts_gaps:
  - corporate.wyndhamhotels.com
  - development.wyndhamhotels.com
  - www.wyndhambusiness.com
  tls_note: |
    www.wyndhamhotels.com negotiates TLS 1.2 while every other host negotiates
    TLS 1.3.
  dmarc_note: |
    wyndhamhotels.com enforces p=reject; wyndhambusiness.com only p=quarantine.

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/wyndham-hotels-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.