SurfaceMap › n › nationalgrid.com

nationalgrid.com

Checked 2026-10-22 10:00 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

fail

10 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !DNSSEC

Problems

  • ✗
    No nameserver responds
    Nameservers · None of the nameserver addresses answered: ns01.nationalgrid.com (65.209.62.102): read udp 46.225.38.91:34778->65.209.62.102:53: i/o timeout; ns02.nationalgrid.com (62.190.154.102): read udp 46.225.38.91:52821->62.190.154.102:53: i/o timeout.
    #14
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Not signed
    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.
    #27

Recent checks

✗

Full report

Domain & DNS report for nationalgrid.com ›

Mail

warn

27 passed 4 warn 0 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC !MX !TLS ✓BIMI

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-003cc501.gslb.pphosted.com, mxb-003cc501.gslb.pphosted.com
    #11
  • !
    1024-bit DKIM key
    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.
    #23
  • !
    Not configured
    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.
    #32

Recent checks

!

Full report

Mail report for nationalgrid.com ›