providesupport.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns-b.providesupport.com, ns-i.providesupport.com, ns-o.providesupport.com; only in the zone: ns-1327.awsdns-37.org, ns-1541.awsdns-00.co.uk, ns-677.awsdns-20.net. ns-1327.awsdns-37.org, ns-1541.awsdns-00.co.uk, ns-426.awsdns-53.com, ns-677.awsdns-20.net, ns-b.providesupport.com, ns-i.providesupport.com, ns-o.providesupport.com report NS ns-1327.awsdns-37.org ns-1541.awsdns-00.co.uk ns-426.awsdns-53.com ns-677.awsdns-20.net.

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns-i.providesupport.com (glue 104.129.90.4, zone 142.202.9.104). Update the glue at your registrar.

SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 20m, retry 2m, expire 14d, negative TTL 3m.

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.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: NS (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 3m; resolvers may use either.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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: mx1.providesupport.com

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

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.