SurfaceMap › m › megagadgets.nl

megagadgets.nl

Checked 2026-10-22 14:30 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

25 passed 3 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration !Delegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Signed but not delegated securely
    DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 12h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for megagadgets.nl ›

Mail

fail

22 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    Multiple SPF records
    SPF · Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:achmed@hypemedia.nl (needs megagadgets.nl._report._dmarc.hypemedia.nl). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 megagadgets.nl ›