SurfaceMap › r › radiotimes.com

radiotimes.com

Checked 2026-10-22 10:24 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.imdserve.com (glue 208.94.148.4, zone 208.94.148.4, 2600:1800:10::1); ns2.imdserve.com (glue 208.80.124.4, zone 208.80.124.4, 2600:1801:11::1); ns3.imdserve.com (glue 208.80.126.4, zone 208.80.126.4, 2600:1802:12::1); ns4.imdserve.com (glue 208.80.125.4, zone 208.80.125.4, 2600:1801:13::1); ns5.imdserve.com (glue 208.80.127.4, zone 208.80.127.4, 2600:1802:14::1); ns6.imdserve.com (glue 208.94.149.4, zone 208.94.149.4, 2600:1800:15::1). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    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.
    #23
  • !
    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 radiotimes.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: eu-smtp-inbound-1.mimecast.com, eu-smtp-inbound-2.mimecast.com
    #11
  • !
    Unreadable DKIM key
    DKIM · These keys could not be parsed, so signatures made with them will fail: default (public key is not valid base64).
    #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 radiotimes.com ›