All findings — worst first

• !WarningDMARCDMARC is recorded but p=none (monitoring only — no protection)

  Start monitoring cloudsales.app →

  • no enforcement record is recommended yet — a scan alone could not confirm that your mail aligns (valid SPF and a DKIM signature), and moving off p=none without that evidence risks silently blocking legitimate mail. Gather aggregate-report evidence first, then step up: evidence before enforcement
  • p=none only monitors — it does not block spoofing
  • no rua= tag: you receive no aggregate reports to measure alignment
  • no np= tag: non-existent subdomains fall back to sp/p — RFC 9989 §4.7's np=reject can protect them now
  • publish a rua= reporting address so receivers send you aggregate reports — the reports are the only evidence that can unlock a stricter policy

  AI explanation

  Your domain has a DMARC setting, but it is only in monitoring mode, so it is not actually blocking fake or forged emails. This matters because attackers can still send messages that look like they came from your domain, which can hurt trust and increase phishing risk. To fix it, change the DMARC policy from monitoring only to an enforcing mode so email receivers are told to reject or quarantine suspicious mail.

Domain owner? Re-scan any time — or email [email protected] to have this page removed.