nycgo.com

SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 1h, 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.

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, mx1.dnsmadeeasy.com, mx2.dnsmadeeasy.com, mx3.dnsmadeeasy.com

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

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc_reports@nyctourism.com (needs nycgo.com._report._dmarc.nyctourism.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.