Public Reviewer Checklist
GCA Domain Email Evidence Checklist
This public page mirrors the owner evidence checklist for the active support@gcagochina.com mailbox before the next clean BaseScan token profile resubmission. It does not publish private mailbox screenshots and does not claim BaseScan token profile approval.
Current Boundary
The active public contact is support@gcagochina.com. DNS, inbound, outbound, and public-site alignment evidence is retained privately for reviewer follow-up.
Reviewer Use
A reviewer can use this page to see the exact evidence gates GCA is collecting, without requiring private mailbox screenshots to be posted on the public website.
Required Evidence Files
Five Files To Save Privately Before Resubmission
domain-email-provider-active.png: mail provider dashboard shows support@gcagochina.com as verified or active.domain-email-dns-mx-spf-dkim-dmarc.txt: MX, SPF, DKIM, and DMARC lookup proof is saved after propagation.domain-email-inbound-test.png: inbound test from Gmail or Outlook to support@gcagochina.com is received.domain-email-outbound-test.png: outbound reply from support@gcagochina.com shows the visible domain sender.support-page-domain-email.png: updated support page shows the same domain email used in the BaseScan form.Execution Order
Do These In Order
- Choose a full mailbox provider that can receive and send as
support@gcagochina.com. - Initialize the local evidence directory with the evidence packet tool.
- Save provider proof showing
support@gcagochina.comactive or verified. - Add provider MX, SPF, DKIM, and DMARC DNS records exactly as supplied by the provider.
- Save DNS proof after the read-only DNS checker reports
readyForBaseScanEmailEvidencetrue. - Send an inbound test from Gmail or Outlook to
support@gcagochina.comand save the received-message proof. - Reply from
support@gcagochina.comback to Gmail or Outlook and save visible-sender proof. - Switch public support/BaseScan email values only after DNS and mail-flow evidence are complete.
- Save
support-page-domain-email.pngshowing the same domain email used in the BaseScan form. - Build
launch/domain_email_evidence_packet.jsonand run the BaseScan resubmission preflight.
Operator Commands
Read-Only And Local Evidence Commands
python3 tools/build_domain_email_evidence_packet.py --init-evidence-dir --evidence-dir launch/domain_email_evidencepython3 tools/check_domain_email_dns.py --domain gcagochina.com --mailbox support --dkim-selector <provider-selector> --jsonpython3 tools/build_domain_email_evidence_packet.py --dkim-selector <provider-selector> --evidence-dir launch/domain_email_evidence --website-email-updated --output-json launch/domain_email_evidence_packet.json --output-md launch/domain_email_evidence_packet.md --jsonpython3 tools/check_basescan_resubmission_readiness.py --json --require-readyStop Conditions
Do Not Submit BaseScan If Any Condition Is True
support@gcagochina.comcannot receive external email.support@gcagochina.comcannot send authenticated replies with the visible sender set to the domain email.- MX, SPF, DKIM, and DMARC DNS checks stop reporting ready.
- Any required evidence file is missing.
- Public support/BaseScan files still publish the old Outlook contact after the switch.
- BaseScan resubmission preflight reports
readyForBaseScanResubmissionfalse.
Boundaries
What This Checklist Does Not Do
No DNS Writes
The checklist does not write DNS records. The owner must enter provider records in the DNS host.
No Email Sending
The checklist does not send email or test mailbox flow automatically.
No BaseScan Submission
The checklist does not submit BaseScan requests or claim BaseScan approval.
No Wallet Actions
The checklist does not touch wallets, contracts, liquidity, private keys, or token transfers.
No Secret Storage
The checklist does not store mailbox passwords, API keys, DNS tokens, or private evidence in public files.
No Private Screenshot Publishing
Private mailbox screenshots and proof files must remain in the git-ignored evidence directory.