ocregister.com

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

DMARC · DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.

DKIM · These keys could not be parsed, so signatures made with them will fail: google (public key is not valid base64).

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:mngtribtest1@gmail.com (needs ocregister.com._report._dmarc.gmail.com). Ask the report provider to publish the record, or check the address.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.