FolioU1AUnit 1
As at
Sun 22 Nov 2026
Entries
12
Not yet
14
Page seal F15B, 008°33′. Drawn from the SHA 256 of this page’s source textF15B
Page sealF15B, 008°33′

Mail Alignment

Quality gate (target)
Sat 5 Dec 2026
First sale (target)
Mon 7 Dec 2026
Turnaround
Within 72 hours of the day you send what we ask for

Stage A of Unit 1, sold on its own. Within 72 hours of the day you send what we ask for, we write the steps that put a domain's mail, registrar and DNS settings right and switch on reporting. At launch this job runs in runbook mode: AI agents check your setup, write each step and test the result; you, or your agency, apply each step; we do not log in to your systems. At launch, a second AI model from another company and a named reviewer under contract will check every job.1 The policy stays at watch only. Nothing is rejected yet. Launch price: 232 USD direct; agencies that resell it pay us 152 USD (wholesale) and set their own price to you. Full price, once we can make the changes ourselves: 290 USD direct, or 190 USD wholesale.

Quality test (Bench) gate: Sat 5 Dec 2026 (target). Not yet: Bench gate passed and sealed2 Until it passes, Mail Alignment is not on sale to anyone outside the firm.

Lines of this unit

LineLaunch priceLaunch price, through a partnerFull price, directFull price, wholesaleGate, target
Mail Alignment (Stage A alone)232 USD152 USD290 USD190 USDSat 5 Dec 2026
Domain and Mail Gap Closure, Stages A and B312 USD200 USD390 USD250 USDSat 5 Dec 2026
Mail Enforcement (Stage B alone)120 USD76 USD150 USD95 USDFri 18 Dec 2026

Who it is for

A business, or the agency that runs its domain, that wants the settings fixed and tested now, and will decide later whether to move to reject. When it is ready, Mail Enforcement takes the domain the rest of the way.

What we do

  • SPF valid with 10 DNS lookups or fewer. SPF is the record that lists which servers may send mail for the domain.
  • DKIM signing switched on for every sender whose DKIM record you or your agency give us. DKIM is a signature each mail carries, checked against a public key.
  • Every other known sender listed in a signed ramp plan, with a hold reason such as "no access to the sender's console".
  • SPF and DKIM aligned with the domain in the visible From line.
  • DMARC at p=none (watch only), with aggregate reports sent to a mailbox on the client's own subdomain.
  • Registrar lock on. DNSSEC on where the registrar supports it.
  • Parked domains that send no mail set to reject.
  • Dangling records removed: aliases that point at a service that is gone.
  • Certificate validity checked. Automating certificates is Unit 2.
  • Every item retested. A signed ramp plan naming every sender seen.

Where the report mailbox goes, and why it points only at the client's own provider: see the report route on the Domain and Mail Gap Closure page. Where the client's tenant blocks forwarding to outside addresses, we use the client's existing DMARC vendor export or a delegated reports subdomain first.3

How it is accepted

The 20 Stage A tests, listed in plain words on the Domain and Mail Gap Closure page, all pass. Each test reads public data only, so anyone can rerun it. When they pass, the record is issued and the warranty clock starts. No test result names a marsadel.com host in the client's records: the keys stay with the client.

Warranty

  • Stage A: we redo it free until every Stage A test passes. If it has not passed within 10 days of the day you send what we ask for, you get a full refund. Time you take to apply a runbook step does not count toward the 10 days.4
  • After Stage A is accepted: if a Stage A test fails within 30 days because our fix was wrong, we redo it free.
  • Who decides the cause: we propose one from a short list (you changed the setting back, your provider changed something, our fix was wrong, or other), with the evidence. You or your partner confirm it. If you disagree, the cause you choose goes on the record.5 We publish how often each cause happens, including other.
  • In runbook mode, if a test fails because a change was applied differently from the runbook, we point to the line, and you apply it again at no extra cost. The clocks pause until it is applied.6

This is the Stage A part of the one Unit 1 warranty rule, word for word.

Runbook mode

The client applies every change from our written runbook, and we hold no write access. At launch every order runs this way; we make changes ourselves only once insurance that covers AI agent work is in place.7 We retest each change within 72 hours of the client telling us it is applied. Time the client takes to apply a step does not count toward the 72 hours or the 10 day refund point, and both clocks pause while we wait for an approval.4 Runbook mode is the launch price, 20 percent under the full price.

Price

The firm's own prices, in US dollars.

DirectWholesale
Mail Alignment, launch price232 USD152 USD
Mail Alignment, full price (once we can make the changes ourselves)290 USD190 USD

Tier shares apply: 100, 85, 55 or 35 percent by the client's region, set from evidence after the order. Full Unit 1, both stages, is 312 USD direct and 200 USD wholesale at launch, and 390 USD and 250 USD at full price. Payment is taken in full at order.8

What the buyer gives

  • The domain, and every service known to send mail as it.
  • Proof of control: a DNS TXT record with a random label we give you, which you delete once we confirm the check; a registrar account export; or runbook mode.
  • For each sender, the DKIM record it shows in its settings, or the reason it cannot be given. (In write mode, once it opens, access to that sender's console instead.)
  • A report route on the client's own provider, an existing vendor export, or a delegated reports subdomain.

What the buyer gets back

  • A written intake list of each gap and the unit that closes it. Once the Domain Passport report is built, this comes as an intake Domain Passport.9
  • A written runbook for every change.
  • The signed ramp plan, naming every sender and every hold reason.
  • A signed Stage A Proof of Fix record with each test, its evidence, the second AI check's verdict and the reviewer's name.10
  • An after file that holds the evidence for the job. Once the Domain Passport report is built, this comes as an after Domain Passport.9

Who checks it

AI agents check the setup, write each step and test the result. At launch the client or their agency applies each step, and we do not log in to the client's systems. A second AI model from a different company checks the work.11 At launch, a named reviewer under contract will review and sign every job.12 Is client data used to train AI? No, unless the client ticks a consent box that allows it.

The Bench

At least 60 graded cases, at least 10 with third party senders, on 10 test domains across at least 5 registrars and DNS hosts, plus public specification samples and the firm's own domains.13 No client data. Pass means at least 95 percent accepted on the first pass by both the second AI check and the human reviewer, and zero cases that would have broken mail or a site. Result: Not yet: cases, cases with third party senders, pass rate, registrar and DNS host spread, date14 If two contracted reviewers are not in place by Wed 2 Dec 2026, the gate and the first sale move one week later.

The spec file

Version 0.1.0 · Status: quality test (Bench) not passed yet

The machine readable spec of this unit. Download it and hash it yourself: the seal below is drawn from its SHA 256.

Acceptance tests in the spec

  1. 01spf_present_singleExactly one TXT record at the domain starts with v=spf1 followed by a space or the end (RFC 7208 s3.2, s4.5).public DNS
  2. 02spf_syntax_validEvery term of every reached SPF record parses (RFC 7208 s4.6.1, s5, s6), redirect and exp appear at most once each, and every include and redirect target has exactly one SPF record (s5.2, s6.1). Not applicable when spf_present_single fails.public DNS
  3. 03spf_lookup_limitThe include, a, mx, ptr, exists and redirect terms across reached records number 10 or fewer, and each mx term names 10 or fewer MX hosts (RFC 7208 s4.6.4). Mechanisms after all are not evaluated and are not counted (RFC 7208 s4.6.2). Not applicable when spf_present_single fails.public DNS
  4. 04spf_void_lookupsLookups that answer nxdomain or nodata number 2 or fewer, counting the TXT lookup of each include and redirect target, the A lookup of each a term, the MX lookup of each mx term and the A lookup of each exists term with no macro, before any all term (RFC 7208 s4.6.2, s4.6.4, s5.7). An a term is counted from its A answer, as for an IPv4 sender (s5.3). Not applicable when spf_present_single fails.public DNS
  5. 05spf_no_pass_allNo reached SPF record has all with the qualifier + or no qualifier (RFC 7208 s5.1); terms after the first all are not evaluated (s4.6.2). Not applicable when spf_present_single fails.public DNS
  6. 06dkim_key_presentAt least one probed selector (the default list plus the selectors given) has a TXT key record with a non empty p= (RFC 6376 s3.6.1, s3.6.2.1). When a mailbox provider is known from MX and has documented selectors, a key must sit at one of them or at a selector the client gave (plan 5.2: DKIM signing on every sender whose console the client gives access to). Not applicable when the domain sends no mail.public DNS
  7. 07dkim_key_strengthEvery found key parses, every found RSA key is 1024 bits or more (RFC 8301 s3.2), no found key allows only sha1 (h= without sha256, RFC 8301 s3.1) and every found key is for mail (s= absent, or naming email or *, RFC 6376 s3.6.1). Not applicable when the domain sends no mail or no key was found.public DNS
  8. 08dmarc_present_singleExactly one TXT record at _dmarc.<domain> starts with v=DMARC1, the v tag name read without case (RFC 7489 s6.6.3 steps 2 and 5, s6.4); or, when the name has no record, exactly one at _dmarc.<org_domain> when org_domain is given, or else at the nearest parent of the name (down to two labels) that has a record, taken as the organizational domain in place of a public suffix list; that record's policy then applies (s6.6.3 step 3).public DNS
  9. 09dmarc_syntax_validv=DMARC1 is the first tag and p the second; p and sp are none, quarantine or reject; adkim and aspf are r or s; pct is an integer from 0 to 100; ri is an integer; fo items are 0, 1, d or s; rua and ruf are comma lists of URIs with an optional size; no tag appears twice, tag names compared without case (RFC 7489 s6.3, s6.4; RFC 6376 s3.2). Not applicable when dmarc_present_single fails.public DNS
  10. 10dmarc_rua_presentrua holds at least one valid mailto URI. An empty tag spec is a syntax fault (test 9) but the other tags are still read. Not applicable when dmarc_present_single fails or the domain sends no mail.public DNS
  11. 11dmarc_rua_authorisedFor each rua mailto address outside the Organizational Domain (the domain, or org_domain when given), <record domain>._report._dmarc.<address domain> has a TXT record starting with v=DMARC1 (RFC 7489 s7.1). Not applicable when there is no valid rua or every rua is under the Organizational Domain.public DNS
  12. 12mx_validMX is a lone null MX (RFC 7505 s3), or every MX exchange answers A or AAAA. Not applicable when the domain has no MX.public DNS
  13. 13parked_no_mail_lockedFor a domain that sends no mail: MX is a lone null MX, the SPF record is v=spf1 -all and DMARC passes dmarc_present_single and dmarc_syntax_valid with p=reject, or sp=reject when inherited (RFC 7505 s4.2). A domain sends no mail when the client says so (mail_use none), or, while the client has not said, when it has no MX or only a null MX, no SPF sender and no DKIM key at the probed selectors; that second case is a guess, so a fail carries a hold until the client confirms. Not applicable when the domain sends mail or the client says it does.public DNS
  14. 14dnssec_signedDS and DNSKEY both answer, a DS key tag and algorithm match the computed key tag (RFC 4034 Appendix B) and algorithm of a DNSKEY, and the DNSKEY answers without checking disabled (a zone that answers only with cd=1 is broken). Read at org_domain when given. Not applicable when there is no DS and the client records that its registrar or DNS host does not support DNSSEC (dnssec_supported false). While support is not recorded, a fail for a missing DS carries a hold and is settled when the client records support or its absence.public DNS
  15. 15registrar_lock_onThe RDAP status list holds client transfer prohibited or server transfer prohibited (RFC 8056 mapping). Read at org_domain when given. Not applicable when the TLD has no RDAP service, when the registry shows no transfer lock status (.uk), or when the client records that its registrar has no transfer lock (registrar_lock_supported false). While support is not recorded, a fail carries a hold.RDAP
  16. 16registration_not_expiringThe RDAP expiration event is at least 30 days after the scan. Read at org_domain when given. Not applicable when the TLD has no RDAP service.RDAP
  17. 17tls_apex_validThe certificate served on the apex is authorized, matches the host name, is already valid and has 14 or more days left. Not applicable when the host has no address or refuses the connection.TLS handshake
  18. 18tls_www_validThe same as tls_apex_valid for www.<domain>.TLS handshake
  19. 19no_dangling_cnameFor each host of the list (given, or the default list), a CNAME target exists: its A lookup does not answer nxdomain.public DNS
  20. 20no_firm_hostNo firm host appears in the MX of the domain, the TXT at the domain and at _dmarc, the CNAME at _dmarc (and at the parent _dmarc when the record is inherited), every SPF record at or under the domain reached from its own SPF record (such as _spf), the rua and ruf address domains, the MX, TXT and CNAME of each rua address domain under the domain, the CNAME of each DKIM selector where a key was found, or the CNAME targets of the host list (plan 5.2 Stage A acceptance test). The firm hosts are marsadel.com and the names under it.public DNS
Seal of this unit’s spec file2FCF

Spec U1A 0.1.0, 2FCF, 139°48′

2fcf6369 1f31dc0f 9b6a9fad 1868de77 356ae419 8fdea2bb 6341f05c 519b0a42

Download the spec file

Not yet in place14

Nothing is on sale yet; each numbered mark on this page points to a condition below. Every condition, with its state, is on the status board.

  1. 1second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  2. 2Bench gate passed and sealed
  3. 3Microsoft and Google forwarding pages read and quoted
  4. 4runbook clock rule confirmed in the terms
  5. 5dispute rule set in the terms, including what happens to the refund while a cause is disputed
  6. 6rule confirmed in the terms
  7. 7cover that includes AI agent work bound
  8. 8company formed and checkout live
  9. 9Domain Passport report built as a Marsadel unit
  10. 10client record signing live in our record log
  11. 11second model vendor connected
  12. 12two contracted reviewers, target Mon 30 Nov 2026
  13. 13Bench test domains registered
  14. 14cases, cases with third party senders, pass rate, registrar and DNS host spread, date

Each item is also marked where it stands on this page.