| Name | What it does | Think of it as |
|---|---|---|
| SPF | Publishes the list of servers allowed to send email for your domain | A staff list for the office entrance |
| DKIM | Adds a signature to each email so receivers can confirm it was not altered and really came from your domain | A company seal on a document |
| DMARC | Declares what receivers should do with email that fails SPF and DKIM for your From domain, and sends you reports | A notice: destroy documents without the right seal |
Adding t=y makes a level a trial: receivers treat it one step weaker. The older pct tag is being phased out.
Yes. SPF and DKIM only check; they don't tell receivers what to do when a check fails, and they don't check that the authenticated domain matches the visible From address. DMARC does both (that matching is called alignment).
Not at p=none (monitor only): nothing changes in delivery. Problems only appear after moving to quarantine or reject if some of your own senders are not set up for SPF or DKIM, which is why you raise the level only after the reports show everything passing.
Whether the domain that passed SPF or DKIM belongs to the same organisation as the From address. If a newsletter service passes DKIM with its own domain while the From address is yours, DMARC still fails.