CHYP.ai · ORBIT // Cloudy_Day Security Suite

🧪 DNS & EMAIL TRUST · Capstone · ~9 min · 80 XP

DNS & Email Trust: kestrel-chat.example

Read SPF and DMARC records for a fictional domain and predict how receivers treat a message.

SIMULATION Generated from the reviewed template dns@1.0.0 (cday-case/1), seed d20261121. Every company, person, domain and IP is fictional.

Evidence

DNS TXT kestrel-chat.example

v=spf1 ip4:192.0.2.0/25 mx include:_spf1.mailer9.example include:_spf2.mailer4.example include:_spf3.mailer1.example include:_spf4.mailer2.example -all

DNS TXT _dmarc.kestrel-chat.example

v=DMARC1; p=none; rua=mailto:dmarc@kestrel-chat.example; adkim=r; aspf=r

DNS MX kestrel-chat.example

10 mx1.kestrel-chat.example.
20 mx2.kestrel-chat.example.

Message under review

A message claiming to be from billing@kestrel-chat.example arrived from IP 192.0.2.11. It has no valid DKIM signature for kestrel-chat.example.

Does kestrel-chat.example's SPF record authorize 192.0.2.11?
What does the DMARC policy ask receivers to do with mail that fails?
How many DNS-querying SPF mechanisms does the record use (include, mx, a, …)?
What's most likely to happen to this message at a DMARC-checking receiver?

Playing as a guest: you'll see your score and the reasoning, but nothing is saved. Join (one click, no email) to earn XP.

Want a different one? New variant ↻

Simulated targets only. For education on simulated targets only; never test systems you don't own or have written permission to test. The Arena is an independent researcher project, not affiliated with or endorsed by any company or agency named. Every company, host and log here is fictional unless a page says it's ORBIT's own public outage data.

Where to next