sweetwater.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net; only in the zone: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net. dns1.p02.nsone.net, dns1.p03.nsone.net, dns2.p02.nsone.net, dns2.p03.nsone.net, dns3.p02.nsone.net, dns3.p03.nsone.net, dns4.p02.nsone.net, dns4.p03.nsone.net report NS dns1.p03.nsone.net dns2.p03.nsone.net dns3.p03.nsone.net dns4.p03.nsone.net.

SOA · expire 30m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 30m must be longer than refresh + retry. Current values: refresh 2h, retry 10m, expire 30m, negative TTL 2h.

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.

MX · The following MX hosts could not be resolved to IPv6 addresses: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits). Rotate to a 2048-bit key.

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.