FolioU1Unit 1
As at
Sun 22 Nov 2026
Entries
16
Not yet
29
Page seal 0755, 031°23′. Drawn from the SHA 256 of this page’s source text0755
Page seal0755, 031°23′

Domain and Mail Gap Closure

Quality gate (target)
Sat 5 Dec 2026
First sale (target)
Mon 7 Dec 2026
Turnaround
Stage A within 72 hours of the day you send what we ask for; Stage B runs to reject or day 120 from Stage A

Unit 1. We close the gaps in a domain's registrar, DNS, mail and certificate settings, then move its mail policy, step by step, from watching to rejecting forged mail. At launch this job runs in runbook mode: AI agents check your setup, write each step for you and test the result. You, or whoever runs your website, apply each step. We do not log in to your systems. At launch, a second AI model from another company will check every step, and a named reviewer under contract will review and sign every job.1 Each step waits for report data and your yes, and a sender that still fails holds the next step. Every runbook step lists the old value of each record it changes, so you can put it back yourself. Other mail servers may keep the new value until the record's cache time (TTL) runs out.2

At a glance. Launch price, when you apply the changes: 312 USD. Agencies that resell this job pay us 200 USD (wholesale) and set their own price to you. Full price, once we can make the changes ourselves: 390 USD, or 250 USD wholesale. These are our own Tier 1 prices. Time: Stage A within 72 hours of the day you send what we ask for. In runbook mode, we retest each change within 72 hours of you telling us it is applied; time you take to apply a step does not count toward the 72 hours or the 10 day refund point.3 Reject comes in about 8 weeks. You give: your domain, the tools that send mail as you, and a written yes at each step. Status: not on sale yet.4

Quality test (we call it the Bench): Sat 5 Dec 2026 (target). Not yet: Stage A Bench passed and sealed5

Stage B gate: Fri 18 Dec 2026 (target). Not yet: Stage B Bench passed and sealed6

Until the Stage A gate passes, this unit is not on sale to anyone outside Marsadel. The first runs are read only, on domains the founder owns and on written test fixtures (example.org style names). The first four, on domains the founder owns, were sealed on 22 Nov 2026 with no change applied and checked by the rule based inspector only; record MSD 0001, the assessment of marsadel.com, can be checked in a browser.

Lines of this unit

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

What it is, in one paragraph

Many small business domains carry old settings left by the last developer or agency. Mail from the domain can be forged. Invoices land in spam. The registrar lock is off. A forgotten alias points at a service that no longer exists. Unit 1 fixes these in two stages. Stage A writes the steps that put the settings right, turns on reporting once you apply them, and lists any sender it cannot reach with the reason. Stage B reads those reports for some weeks and raises the policy until forged mail is rejected. Each step waits for clean report data, and a known sender that still fails holds the next step.

What you give us

At launch you, or your web person, apply every change from our written steps. We do not log in to your systems.

  • Your domain name, and every service known to send mail as your domain, such as your invoicing tool.
  • Proof of control, by one of three routes: 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, where you apply every change.
  • For each sending service, the DKIM record it shows you in its settings, or the reason you cannot get it. A sender without one is listed with a hold reason, not dropped. (In write mode, once it opens, access to that service's console instead.)
  • A report route: an alias on your own mail provider, an existing DMARC vendor's export, or a delegated reports subdomain.
  • A written approval at each Stage B step.
  • In runbook mode, the applied changes, confirmed one by one.
  • Some of your time, or your web person's, spread over a few days. The minutes are not measured yet; we print the median after the Bench runs.7

If you want to stop

If a change stops some of your mail

Stage A: alignment, within 72 hours

Stage A covers these steps.

  • SPF (the record that lists which servers may send mail for the domain) is valid and makes 10 DNS lookups or fewer.
  • DKIM (a signature each mail carries, checked against a public key) is switched on for every sending service whose DKIM record you or your agency give us (or, in write mode, whose console you give us access to).
  • Every other known sender is listed in the signed ramp plan with a hold reason, for example "no access to the sender's console".
  • SPF and DKIM alignment: the domain in the visible From line matches the domain that passed the check.
  • DMARC (the policy that tells receivers what to do with mail that fails) is set to p=none, which means "watch only", with daily reports sent to a mailbox on your own subdomain.
  • Registrar lock is on, so the domain cannot be moved to another registrar without a deliberate unlock.
  • DNSSEC (signed DNS answers) is on where the registrar supports it.
  • Parked domains that send no mail are set to reject all mail sent in their name.
  • Dangling records are removed. A dangling record is an alias that points at a service that is gone, which someone else could claim.
  • Certificate validity is checked. Automating certificates is Unit 2.
  • Retest of every item above.
  • A signed ramp plan naming every sender seen.

Where the reports go

DMARC reports go to an address on your own mail provider, for example an alias on a reports subdomain in your own Google or Microsoft account. The alias forwards to our intake with the provider's signature intact.8 The reports subdomain points only at your own provider. Because it sits under your own domain, no outside authorisation record is needed. Setting the MX record of that subdomain is a manual runbook step.

Some tenants block automatic forwarding to outside addresses by default. Microsoft 365 does this, and Google Workspace needs an admin routing rule.9 Where the tenant blocks outside forwarding, we offer two other routes first. One: if you already use a DMARC vendor, we take the vendor's export by API instead of adding a second report address. Two: you create a mailbox on a reports subdomain you hand to a mail provider you choose. Where you do choose a forwarding rule, the runbook scopes it to the one report alias only, it has its own acceptance test, and the clocks pause while it is set.10

There is no shared mailbox fallback on a Marsadel domain. A shared report domain would list all our clients, you included, in public DNS. Stage B cannot start without a working report route.

Stage A acceptance tests

Stage A is accepted when the 20 tests of the Stage A spec pass. Each one reads public data only: public DNS, the public registration record (RDAP) and the certificate a site presents, so anyone can rerun them. The test sheet at the foot of this page lists every test with what it checks and where its evidence comes from, beside the spec file to download.

Stage B: the staged ramp

Stage B moves DMARC from watch only to quarantine (send failing mail to spam) and then to reject (refuse failing mail).

  • Quarantine after 14 days of clean reports, counted from the first full report day after Stage A ends.
  • Reject after a further 42 days, the last 30 of them with mail from senders you have not approved under 1 percent.
  • Each step is an approval. You or your agency approve it in writing before it happens.
  • A sender that still fails holds the ramp. We write down the hold reason and wait, instead of letting your invoices bounce.
  • The end point. Stage B runs to reject or to day 120 from Stage A, whichever comes first.

The 42 day step is our own design. Red Sift says quarantine to reject typically takes 6 to 8 weeks; DuoCircle suggests under 1 percent unknown traffic for 30 days before reject, and gives 30 to 90 days from quarantine to reject (both read 22 Nov 2026, S28).

How long it takes, and why it is slower than some

From the day you send what we ask for to reject, the ramp takes about 8 weeks. Here is the arithmetic for an order where everything we ask for arrives on day 0.

DayEvent
0What we ask for arrives
3Stage A ends (72 hours)
4First full report day
18Quarantine, after 14 clean report days
60Reject, 42 days later

For an order placed on Mon 11 Jan 2027, that gives Stage A ended 14 Jan, quarantine 29 Jan and reject 12 Mar 2027. Holds and approvals can move each date later. Holiday weeks can too.

Others are faster on paper. Valimail states a 45 day median to enforcement (S22). O365HQ sells the move from watch only to reject in about four monitored weeks (S24). Our ramp is slower because we wait for 30 days with mail from senders you have not approved under 1 percent before reject. That wait is what lets a forgotten billing or helpdesk sender show up in the reports before it starts bouncing.

Acceptance events

  • Stage A is accepted when its tests pass. The record is issued and the warranty clock starts.
  • Stage B is accepted at the policy the report data allows, with any hold reason written down. It gets its own record.
  • Rechecks run at 30, 90 and 365 days after reject. They rerun the tests stored on the record.

The warranty rule

This is the one warranty rule for Unit 1. The how it works page, the price book and every record carry the same rule, and our terms set it out in legal form.11

  • 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.3
  • After Stage A is accepted: if a Stage A test fails within 30 days because our fix was wrong, we redo it free.
  • Stage B: if reject is not reached by day 120 because our fix was wrong, we refund the Stage B share. In Tier 1, in runbook mode, that is 120 USD direct or 76 USD wholesale; at full price it is 150 USD direct or 95 USD wholesale. Other tiers get the same share of their lower price. It is not more than you paid.
  • Rechecks: we recheck at 30, 90 and 365 days after reject. If a 30 or 90 day check fails because our fix was wrong, we redo it free and credit you 30 percent of the price paid. If a 365 day check fails for that reason, 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.12 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.13

The Stage A lines also cover Mail Alignment bought on its own. The 30 percent credit comes from a reserve we fund.14

Runbook mode

In runbook mode you apply every change from our written runbook. We hold no write access to your registrar, DNS or mail.

  • At launch every order runs in runbook mode. We make changes ourselves only once insurance that covers work done by AI agents is in place, and you can still choose runbook mode after that.15
  • Stage A runs within 72 hours of the day you send what we ask for. We retest each change within 72 hours of you telling us it is applied. Time you take to apply a step does not count toward the 72 hours or the 10 day refund point.3
  • Both clocks pause while we wait for your approval, and restart when it arrives.
  • In write mode, once it opens, both clocks also pause whenever we ask for access to a sender's console, and restart when access arrives.
  • Runbook mode is the launch price: 312 USD direct, 200 USD wholesale, 20 percent under the full price.

Price

These are our own prices, in US dollars. At launch you pay the launch price, because you apply the changes.

LineLaunch priceLaunch price, through a partnerFullFull wholesale
Unit 1, both stages312 USD200 USD390 USD250 USD
Mail Alignment alone (Stage A)232 USD152 USD290 USD190 USD
Mail Enforcement alone (Stage B)120 USD76 USD150 USD95 USD

Full: full price (once we can make the changes ourselves); Full wholesale: full price, wholesale (through a partner, once we can make the changes ourselves).

  • Direct is the price to a business that orders for itself. Wholesale is the price to an agency or IT firm that resells the work to its own client.
  • Tiers. Direct prices are Tier 1 list prices: US, Canada, UK, Ireland, Australia, New Zealand, the German speaking countries, the Nordics, Japan and the Gulf. Tier 2 pays 85 percent: France, Belgium, Spain, Italy, the Netherlands. Tier 3 pays 55 percent: Latin America and Eastern Europe, Poland included. Tier 4 pays 35 percent: India, Indonesia, the Philippines and Africa.
  • How the tier is set. When you start an order, we read where your mail and hosting sit, the country in the registration record where shown, and your site's language, and show your price before you pay. Tier 1 when the signals conflict. A reseller serving a Tier 1 client pays Tier 1 for that client.
  • Tier 4 orders of Unit 1 open later.16
  • Payment is taken in full at order, in US dollars, by card or by USDC invoice (USDC is a digital token worth one US dollar). Refunds go back the way you paid.17

Against the market

Printed prices for this work run from near 50 USD a domain to about 1,400 USD for a full move to reject on one domain. We print the range with each source and the date we read it.

SellerWhat it statesSource, read 22 Nov 2026
Fiverr gigs for SPF, DKIM and DMARCnear 50 USDS25, a search result18
O365HQ monitoring95 USD per monitored domain a month; monitoring only, for a domain already set up; setup is a separate projectS24, search result 22 Nov 2026, not yet opened19
O365HQ ramp450 USD per domain plus a 950 USD tenant fee, about a 4 week rampS24, page reread
DMARC Report managed tierA fixed one time price per domain, given on request; enforcement within 90 days in writingS23, search result 22 Nov 2026, not yet opened19
Valimail45 day median to enforcementS22, read 22 Nov 2026

Unit 1 covers the registrar lock, DNSSEC, certificate checks, dangling records, the signed record, rechecks and the payout written into the warranty. Compare that list with the scope each gig page states.

Why now

  • Gmail requires bulk senders, close to 5,000 messages or more a day to personal Gmail accounts counted across the primary domain, to publish DMARC with p=none as the floor and to align the From domain (S14). Once a sender crosses that line it counts as a bulk sender from then on.
  • Outlook.com has sent non compliant high volume mail to Junk since 5 May 2025 (S15).
  • Reject has its own reasons: spoofing and invoice fraud sent from your domain, insurer questionnaires that ask about DMARC, and BIMI, which shows a brand logo in the inbox only at enforcement.20

What you get back

  • A written intake list that dates what the last provider left and lists each gap with the unit that closes it. Once the Domain Passport report is built, this comes as an intake Domain Passport.21
  • A written runbook for every change, in the order to apply it.
  • The signed ramp plan, naming every sender seen and every hold reason.
  • A signed Stage A Proof of Fix record: each test with its result, the evidence it read, the second AI check's verdict and who reviewed it.22
  • A signed Stage B Proof of Fix record at the policy reached.
  • An after file that holds the evidence for your job. It carries the code anyone can scan to check your record. Once the Domain Passport report is built, this comes as an after Domain Passport.23
  • Rechecks at 30, 90 and 365 days after reject, with the warranty bound to each.

Who does the work, and who checks it

AI agents check your setup, write each step of the runbook, test the result and draft the record. At launch you or your agency apply each step, and we do not log in to your systems. A second AI model, from a different company, checks the work.24 At launch, a named reviewer under contract will review and sign every job.25 Is your data used to train AI? No, unless you tick a consent box that allows it. Full human review stays on every client unit until 200 graded units in a row show agent error at or below human error. After that, some units are sampled; your record always says whether a human reviewed your unit, and names that person when one did.

The Bench

No step runs on a client's domain before that step's Bench passes. The Bench is a set of graded cases. It will be built from test domains registered for the purpose, with faults injected, plus written fixtures, public specification samples and our own domains. It holds no client data.26

  • Stage A Bench: at least 60 cases, at least 10 of them with third party senders, on 10 test domains across at least 5 registrars and DNS hosts. A third of the fault scripts are written by a reviewer the builders do not see.
  • Stage B Bench: 50 cases built from synthetic aggregate reports in the public report format. No domain reaches reject before this gate, so the reject decision is graded on synthetic cases first and regraded on the first real reject with traffic.
  • Pass means at least 95 percent of cases accepted on the first pass by both the second AI check and a contracted human reviewer, zero cases where the change would have broken mail or a site, and every acceptance test machine checkable.
  • Result: Not yet: cases, cases with third party senders, pass rate, registrar and DNS host spread, date27
  • If a later gate fails, that step's share of the price is refunded at once.
  • If the gate slips. If two contracted reviewers are not in place by Wed 2 Dec 2026, this gate and the first sale move one week later. The same applies if the test sender rig and report mailboxes are not ready.28

Order dates

  • Full Unit 1 orders open with the Stage A gate, with the Stage B gate date printed on the order page. Target: Mon 7 Dec 2026. 29
  • A full order placed on 7 Dec could reach its first Stage B step about 25 Dec. Over the holiday weeks we hold approvals until you are back, and the clock pauses.

With Marsadel the keys stay in your name, the result is rechecked after the work, and the price is printed before you order.

Sources

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 place29

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. 2old value printed on every runbook step
  3. 3runbook clock rule confirmed in the terms
  4. 4Stage A quality test passed
  5. 5Stage A Bench passed and sealed
  6. 6Stage B Bench passed and sealed
  7. 7median client minutes per Stage A from the Bench runs
  8. 8report intake mailbox set up; no Marsadel mailbox exists yet
  9. 9Microsoft and Google pages read and quoted
  10. 10forwarding rule step and its test written into the runbook
  11. 11terms published
  12. 12dispute rule set in the terms, including what happens to the refund while a cause is disputed
  13. 13rule confirmed in the terms
  14. 14recheck reserve funded
  15. 15cover that includes AI agent work bound
  16. 16review time per unit low enough to serve this tier at its price
  17. 17company formed and checkout live
  18. 18pages read in full
  19. 19page read in full
  20. 20each reason checked against a primary source
  21. 21Domain Passport report built as a Marsadel unit
  22. 22client record signing live in our record log
  23. 23per record verify lookup live; Domain Passport report built as a Marsadel unit
  24. 24second model vendor connected
  25. 25two contracted reviewers, target Mon 30 Nov 2026
  26. 26Bench test domains registered
  27. 27cases, cases with third party senders, pass rate, registrar and DNS host spread, date
  28. 28sender rig and report mailboxes for the test domains in place
  29. 29Stage A gate passed; company formed and checkout live

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