OBSERVED_
Read by a machine
13claims
- 13LIVE_
- 0IN LOG_
- 0NEXT_
- 0BROKEN_
- 0UNREAD_
Sheet 8 of the atlas
FLEET PULSE // 90 DAYS
Up all dayPart of the dayMajor outageUnreadOne cell a day from our pulse feed. Green: up 99.95% of the day or more. Amber: 80% to under 99.95%. Red: under 80%. Hollow: unread. Verify →
The claims listed here are about how this site is run. Each one shows its state, the time it was last checked, and how you can check it yourself. Where a machine can read a claim over the public network, a machine does. Where it cannot, we say who read it and how.
Other pages still carry statements that are not on this list yet. Until they are, read them as our word, not as a checked claim.
LIVE means it is on and acting. IN LOG means it is built and watching, and refuses nothing. NEXT means it is not live. BROKEN means its check failed. UNREAD means its check could not run, or is too old (a week for machine checks, 30 days for a dated hand check), and it never means the claim passed.
States are read when the site is released and shown with the time of that check, not between releases. A claim whose check could not run, or is older than a week for a machine check or 30 days for a dated hand check, shows UNREAD, which never means it passed.
Each value says where it was read.
Routes out of dareakt.com. States are read when the site is released and shown with the time of that check, not between releases.
The names and the mail records of dareakt.com
6 of 6 live
What dareakt.com serves, and how it is protected
11 of 11 live
What we watch on our own server
7 of 9 live
Signing in, and the steps still to come
7 of 10 live
Magenta is held back for BROKEN_ and UNREAD_ alone. UNREAD never means passed.
The claims on this list carry one of three classes. Evidence can lower a class; wording never raises it.
Read by a machine
13claims
Read from inside
23claims
A promise
0claims
Read by a machine over the public network
The strongest class, because you can repeat the check.
Read from inside, and said so
Operator checks are marked as such.
A promise
The weakest class.
The names and the mail records of dareakt.com
6/6livedareakt.com is signed with DNSSEC, so a validating resolver can detect forged answers about it.
Run delv @185.12.64.2 dareakt.com SOA and look for the words fully validated.
Read with delv through two named resolvers, 185.12.64.2 and 185.12.64.1, at each release.
Last check: passed, 20 Nov 2026, 06:07 UTC
The key that signs these claims is also named in a DNSSEC-validated DNS record.
Run delv @185.12.64.2 _site-claims.dareakt.com TXT and look for fully validated and the spki-sha256 fingerprint.
Read with delv through two named resolvers at each release. The TXT record must carry the SPKI SHA-256 of the site-claims public key.
Last check: passed, 20 Nov 2026, 06:07 UTC
The key that signs HALLMARK_ certificates is also named in a DNSSEC-validated DNS record.
Run delv @185.12.64.2 _hallmark.dareakt.com TXT and look for fully validated and the spki-sha256 fingerprint.
Read with delv through two named resolvers at each release. The TXT record must carry the SPKI SHA-256 of the hallmark public key. Published at deSEC on 2026-11-07 at 21:11 UTC.
Last check: passed, 20 Nov 2026, 06:07 UTC
dareakt.com publishes an SPF record that names its own mail server as the sender.
Run dig +short TXT dareakt.com and look for a v=spf1 record that names mail.dareakt.com.
Read from the public DNS record at each release.
Last check: passed, 20 Nov 2026, 06:07 UTC
dareakt.com publishes two DKIM keys for its mail, one RSA and one Ed25519.
Run dig +short TXT on v1-rsa-20260912._domainkey.dareakt.com and on v1-ed25519-20260912._domainkey.dareakt.com.
Both selector records are read from the public DNS and each must hold a non-empty key at each release.
Last check: passed, 20 Nov 2026, 06:07 UTC
dareakt.com publishes a DMARC policy telling receivers to quarantine mail that fails its checks.
Run dig +short TXT _dmarc.dareakt.com and look for p=quarantine or p=reject.
Read from the public DNS record at each release: the policy must be quarantine or reject.
Last check: passed, 20 Nov 2026, 06:07 UTC
What dareakt.com serves, and how it is protected
11/11livedareakt.com accepts encrypted connections over TLS 1.3.
Run openssl s_client -connect dareakt.com:443 -tls1_3 and look for a completed handshake.
A handshake limited to TLS 1.3 is made at each release.
Last check: passed, 20 Nov 2026, 06:07 UTC
dareakt.com publishes a security.txt saying how to report a vulnerability, with a future expiry date.
Open dareakt.com/.well-known/security.txt and read the Contact and Expires lines.
The file is fetched and its Expires line read at each release.
https://dareakt.com/.well-known/security.txt
Last check: passed, 20 Nov 2026, 06:07 UTC
The public site pages of dareakt.com are served with an enforced Content Security Policy allowing no unsafe-inline.
Run curl -sI https://dareakt.com/ and read the Content-Security-Policy header: it holds no unsafe-inline. The apps under /apps/ are not covered by this claim.
The Content-Security-Policy header of five public site pages (home, FORGE, SECURITY, PASSWORDLESS and MAIL) is read at each release. App pages are not read.
Last check: passed, 20 Nov 2026, 06:07 UTC
The browser refuses fetch, XHR and WebSocket requests from our public pages to any site not on our approved list.
Run curl -sI https://dareakt.com/ and read the Content-Security-Policy header: connect-src lists only this site and our own pouch, silo and kairos hosts. Images and frames have their own lists, a page can still navigate to any address, and the apps under /apps/ are not covered by this claim.
The enforcing Content-Security-Policy header of five public site pages (home, FORGE, SECURITY, PASSWORDLESS and MAIL) is read at each release, and every connect-src source must be on the approved list. App pages are not read.
Last check: passed, 20 Nov 2026, 06:07 UTC
Page code refuses any signing key missing from its pinned list. This cannot stop an attacker controlling our server.
Fetch the public page-code files that check signatures and read their pinned key list: it must hold at least one key, and the signature file must say pinning is enforced.
Three public files are fetched at each release: https://dareakt.com/core/kernel/daKeyPin.js and https://dareakt.com/core/kernel/daSecurityEnclave.worker.js must each hold a key in their pinned list, and https://dareakt.com/core/daSig.js must say pinning is enforced. All three must match, or the claim reads broken.
https://dareakt.com/core/kernel/daKeyPin.js
Last check: passed, 20 Nov 2026, 06:07 UTC
Page code trusts no file hash unless a pinned key signed it. This cannot stop an attacker controlling our server.
Fetch the public page-code files and read their text. The trust loader must open its pin function with the guard line, name the pin call exactly twice (a function check and the one call, so no alias or second route under that name) and hold no block comments; the signature file must carry the line saying registry verification is enforced and export the verifier. This reads served text and does not run it. Each release also runs the verifier itself on the signed list and on a copy with one hash changed, which it must refuse.
Two public files are fetched at each release and read as text: https://dareakt.com/core/boot.trust.js must open pinVerified with its guard line, name pinCert exactly twice (a function check and the one call) and hold no block comments, and https://dareakt.com/core/daSig.js must carry the enforced line and export verifyRegistry. Both must match, or the claim reads broken. The release also runs the verifier itself; that run is not read from the site.
https://dareakt.com/core/boot.trust.js
Last check: passed, 20 Nov 2026, 06:07 UTC
Every site on FLEET_ is served by the same engine, which picks the site from the host name.
Operator check: read the code that serves requests; it must map each host name to one site of the same engine.
At each release the engine's request code is read and must still choose the site from the host name. It does not read what any site serves.
Last check: passed, 20 Nov 2026, 06:07 UTC
Each page is a JSON file naming its modules, rendered to HTML by the engine before any script runs.
Operator check: read the build code; it must load each page from its JSON file and render its modules into the page HTML.
At each release the build code is read and must still render a page's modules from its JSON file into the page HTML. Whether a given page is correct is not read.
Last check: passed, 20 Nov 2026, 06:07 UTC
The organs plate attaches the runtime's health organs in your browser, and shows any it cannot read as unread.
Operator check: read the code of the organs plate; it must attach the organs in the browser and mark any it cannot read as unread.
At each release the code that attaches the organs in the browser is read, and must still do so and still mark an unreadable one as unread. What each organ measures is described on NERVOUS SYSTEM_; this check does not read the organs, and does not read which page mounts the plate.
Last check: passed, 20 Nov 2026, 06:07 UTC
A booking request is stored in our own database; the guest is emailed a receipt and the owner the request.
Operator check: read the booking request code; it must store the request, then email the owner the request and the guest a receipt.
At each release the booking request code is read and must still store the request and send both emails. That an email is delivered is not read.
Last check: passed, 20 Nov 2026, 06:07 UTC
The owner confirms or declines a request in the site's own admin panel, and the guest is emailed the answer.
Operator check: read the booking admin code; a confirmed or declined status must email the guest.
At each release the booking admin code is read and must still email the guest when a request is confirmed or declined. That an email is delivered is not read.
Last check: passed, 20 Nov 2026, 06:07 UTC
What we watch on our own server
7/9liveEvery site we host is checked for uptime every five minutes, from our own server.
Operator check: read the newest uptime check of each site on record; every one must be less than fifteen minutes old.
At each release the newest uptime check of every site that has one in the last 24 hours is required to be under fifteen minutes old. The five-minute interval is the engine's schedule, read by the operator, not measured here.
Last check: passed, 20 Nov 2026, 06:07 UTC
For each source, a scheduled test restores the newest backup when our server can open it, and logs every result.
Operator check: read the backup audit log. The test picks the newest copy of each source, and that copy needs a successful test restore inside its schedule: weekly for most, monthly for the largest platform database. A newest copy that is sealed cannot be opened on the server, so its turn is logged as left to the hand drill. A source that holds a backup only when the operator takes one by hand (adhoc) is not counted while it holds none. Mail backups are not in this test.
At each release every backup with a rehearsal in the last 90 days needs, inside its schedule plus two days, either a successful restore or, for a sealed copy, a logged hand-off to the drill. A source that holds a backup only when the operator takes one by hand is not counted while it holds none; every scheduled source is. A single overdue backup breaks the claim. Since 6 Nov 2026 new copies are sealed with an offline key the server does not hold.
Last check: passed, 20 Nov 2026, 06:07 UTC
Sealed backups are test-restored by hand with the offline key at least every 90 days.
Hand check: the person holding the offline key restores each sealed backup source in one sitting and dates the drill. A drill older than 90 days no longer counts.
Not met yet: the first one-sitting drill of every sealed source is due after 8 Nov 2026.
Last check: target not met yet, 20 Nov 2026, 06:07 UTC
The databases that hold our sites' data are backed up every night.
Operator check: read the backup log; the newest finished backup of each database that holds site data must be less than 26 hours old.
At each release the newest finished backup of each listed database is required to be under 26 hours old. The nightly schedule is the engine's, read by the operator, not measured here.
Last check: passed, 20 Nov 2026, 06:07 UTC
Our target after losing our server: at most a day of database records lost, your site back within four hours.
Operator check: read our written backup and recovery policy; it must still set this target.
At each release the written backup and recovery policy is read and must still set this target. Whether a restore meets it is shown by the restore rehearsals, not by this check.
Last check: passed, 20 Nov 2026, 06:07 UTC
Once we delete your data, its last backup copy is gone within about 50 days.
Operator check: read the backup log, the list of daily snapshots kept off our own server and the list of mail backups; no copy, snapshot or mail backup may be older than its limit, and every backed-up source must have an active schedule.
The clock starts when your data is deleted from our live systems, not when you leave. Databases are kept for 3 nights, site files for 4 weeks, server settings for 30 nights and mail for 14 nights. The off-site storage keeps its own daily snapshots for 20 days more. At each release no copy may be older than 31 days, no snapshot older than 21 days and no mail copy older than 15 days, and a snapshot or mail file that is not one of the automatic ones breaks the claim. A deleted backup record whose off-site copy still exists counts as a copy.
Last check: failed, 20 Nov 2026, 06:07 UTC
Every backup copy of your data that we keep off our own server is encrypted.
Operator check: read the backup upload setting and the file store setting on the server; backups must go through the encrypting storage and uploads must be encrypted at rest.
Read from the server settings at each release: backup copies go to the off-site storage through an encrypting remote, mail copies are encrypted on the mail server and the upload refuses any that is not, and the file store encrypts SILO, FRAME, INK and LEDGER uploads at rest. Nearly all older files of these kinds and the file store's preview pictures also have encrypted copies, but their plain copies stay until we remove them. Since 6 Nov 2026 each new copy kept on our own server is sealed as it is written; older copies there stay plain until they roll off, and the disks of our server are not encrypted.
Last check: passed, 20 Nov 2026, 06:07 UTC
VAT returns are prepared in Tax Reporter every month.
Operator check: read whether a VAT return is prepared in Tax Reporter for the period due: the previous calendar month once today is after the 25th (the Czech filing deadline), otherwise the month before that. Only the year and month of a return are read, never a client, an owner or a figure.
At each release the database is asked for one thing: whether a VAT return prepared in Tax Reporter exists for the period due, across all accountants and clients. That is the previous calendar month once the date is past the 25th, and the month before that until then. Without one, the claim breaks. It reads the year and month only, and it does not prove a return was filed with the tax office.
Last check: passed, 20 Nov 2026, 06:07 UTC
Sokol Lustenice's results reach the club site after every match weekend, read from the Czech FA.
Operator check: read the saved copy of each league's matches from the Czech FA. For each league, take its latest weekend match (Saturday or Sunday) dated more than three days ago; the copy must hold that match's score or have been fetched after that match day. A league with no such match passes. Weekday matches are not counted. A match date that cannot be read fails. Whether each score is right is not checked.
At each release, on the machine that runs it, every saved copy of a league's matches is read for its latest weekend match more than three days old: the copy must hold that match's score, or have been fetched after that match day. A copy with neither breaks the claim, and so does a match date that cannot be read. It does not check that each score is right.
Last check: passed, 20 Nov 2026, 06:07 UTC
Signing in, and the steps still to come
7/10livePlatform admins can sign in to dareakt.com with a passkey.
Operator check: read the passkey sign-in setting on the server; it must list dareakt.
Read from the server settings at each release: the sign-in flag lists dareakt and passkeys are not switched off.
Last check: passed, 20 Nov 2026, 06:07 UTC
Platform admins can register passkeys for their accounts.
Operator check: read the passkey registration setting on the server; it must not be off.
Read from the server settings at each release: passkey registration is not switched off.
Last check: passed, 20 Nov 2026, 06:07 UTC
Platform admins can be held to passkey-only sign-in.
Operator check: read the passkey registration setting on the server; with it off, a stored policy is paused.
Read from the server settings at each release: a passkey-only policy is paused whenever passkey registration is off.
Last check: passed, 20 Nov 2026, 06:07 UTC
Sign-in approval from your phone, with the glyph dial, runs on its own separate origin.
Open gate.dareakt.com in a browser and see the TESSERA approval device, with its dial, answer there on its own origin, apart from dareakt.com.
The phone gate page at gate.dareakt.com is fetched at each release and must answer with the TESSERA approval device.
Last check: passed, 20 Nov 2026, 06:07 UTC
Adding a sign-in factor to an account with one starts a 24-hour wait, with listed exceptions; the owner is told.
Operator check: read the factor delay constant in the sign-in code; it is 24 hours. These count at once: a fresh set of emergency sequences, and a key, phone gate or authenticator landed through account recovery or an operator re-key, which pass their own checks first.
The delay constant is read from the source at each release. The owner notice was traced through the code by hand on 3 Nov 2026.
Last check: passed, 20 Nov 2026, 06:07 UTC
Sign-in allows 5 tries a minute per IP; 5 failures in a row lock the account, up to an hour.
Operator check: read the sign-in limiter and the lockout constants in the sign-in code: 5 tries per IP, refilled over a minute; after 5 failures in a row a lock of one minute that doubles up to one hour.
The limiter and lockout constants are read from the released source at each release. If the database cannot be reached, the account lock is skipped and the per-IP limit still applies.
Last check: passed, 20 Nov 2026, 06:07 UTC
Every session cookie is checked against the sign-in policy; a session that does not meet its person's policy is refused.
Operator check: read the session policy setting on the server; it must read enforce.
Read from the server settings at each release: the session policy check is in enforce mode.
Last check: passed, 20 Nov 2026, 06:07 UTC
The passwordless recovery steps for ordinary accounts are built and run in log mode, refusing nothing.
Operator check: read the recovery sequence setting on the server; it must read log.
Read from the server settings at each release: the recovery sequence flag is in log mode, not enforce.
Last check: failed, 20 Nov 2026, 06:07 UTC
An account can have its password switched off, leaving passkeys as its only way in.
Operator check: look in the sign-in code for a switch that turns a password off.
Not built yet. Today the platform only checks whether an account could safely go without its password; nothing switches a password off.
Last check: no machine check, moved by hand
New people can join through an invite that sets up a passkey, with no password.
Operator check: read the walk-in invite setting on the server, and each setting the invites depend on (account recovery, passkey sign-up and passkey sign-in); every one must read enforce for everyone.
Built and switched off. It turns on once account recovery and passkey sign-up are on for everyone; the check reads the server's invite setting at each release.
Last check: target not met yet, 20 Nov 2026, 06:07 UTC
You can verify it without trusting this page.
Verify it yourself →The same list is published as one signed file.
One file, signed with an Ed25519 key
The file holds the claims, their states and the times of their checks, in English and in Czech.
Five steps on any machine with curl, python3, openssl 3 and delv
A good file prints Signature Verified Successfully. The signed text is the payload field byte for byte, so do not reformat it. Any other answer means the file is not the one we signed.
The Czech statements are in the signed file, beside the English ones.
A signed certificate for the machine-read claims, with its own check, is at https://dareakt.com/hallmark
The name site-claims is provisional. It is not a registered standard, and it may change or be replaced.
The record does not flatter. What is unproven is named unproven.