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.
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.
| Line | Launch price | Launch price, through a partner | Full price, direct | Full price, wholesale | Gate, target |
|---|---|---|---|---|---|
| Mail Alignment (Stage A alone) | 232 USD | 152 USD | 290 USD | 190 USD | Sat 5 Dec 2026 |
| Domain and Mail Gap Closure, Stages A and B | 312 USD | 200 USD | 390 USD | 250 USD | Sat 5 Dec 2026 |
| Mail Enforcement (Stage B alone) | 120 USD | 76 USD | 150 USD | 95 USD | Fri 18 Dec 2026 |
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.
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
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.
This is the Stage A part of the one Unit 1 warranty rule, word for word.
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.
The firm's own prices, in US dollars.
| Direct | Wholesale | |
|---|---|---|
| Mail Alignment, launch price | 232 USD | 152 USD |
| Mail Alignment, full price (once we can make the changes ourselves) | 290 USD | 190 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
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.
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.
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
spf_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 DNSspf_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 DNSspf_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 DNSspf_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 DNSspf_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 DNSdkim_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 DNSdkim_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 DNSdmarc_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 DNSdmarc_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 DNSdmarc_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 DNSdmarc_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 DNSmx_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 DNSparked_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 DNSdnssec_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 DNSregistrar_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.RDAPregistration_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.RDAPtls_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 handshaketls_www_validThe same as tls_apex_valid for www.<domain>.TLS handshakeno_dangling_cnameFor each host of the list (given, or the default list), a CNAME target exists: its A lookup does not answer nxdomain.public DNSno_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 DNSSpec U1A 0.1.0, 2FCF, 139°48′
2fcf6369 1f31dc0f 9b6a9fad 1868de77 356ae419 8fdea2bb 6341f05c 519b0a42
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.
Each item is also marked where it stands on this page.