trivago.co.kr
Observed Aug 20, 2026, 08:41 UTC (20h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
Cloudflare
Microsoft 365
Facebook/Meta
Google Search ConsoleSteady. No change on record for trivago.co.kr in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
HTTPS probe
A security layer answered instead of the site. That is a working defence doing its job, and we record it as its own state rather than as a failure.
It does NOT mean the site is down or misconfigured. It also does not mean we were treated as hostile - most rules of this kind refuse every non-browser client alike.
- A WAF or bot-management rule refuses non-browser user agents by default.
- Automated traffic from datacenter networks is challenged as a matter of policy.
These are the known causes, not a diagnosis of this domain. We recorded that nothing answered; we did not measure why.
Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS records 19
TLS certificates 0
None.
Subdomains 1
1 subdomain hostname observed and signed - the list itself is part of the paid record.
Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.
Verify this receiptEd25519 receiptthe raw cryptographic proof
- Receipt ID
rcpt_be2e899078af0b9b- Output Hash
99247d03dbd576fe19fc4593629f26363693159555a5a8f711eaef61890e2b00- Signature
ed25519:d4612fdfcaa49a81bec80f3a71253034614c0009f274104e8e2f28b98358750a5d84465f2b776b86e06b9ceaeb07152eccfca7abadcae56ba53f75c7ebc7d905- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast