SurfaceMap › l › locksecure.nl

locksecure.nl

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

Domain & DNS

error

23 passed 3 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.ispnoc.nl (glue 136.144.199.223, 2a01:7c8:d000:477::1, zone 136.144.199.223, 2a01:7c8:d000:477:5054:ff:fe2b:6b6c). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #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 locksecure.nl ›

Mail

fail

19 passed 5 warn 1 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
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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:dmarc@ispnoc.net (needs locksecure.nl._report._dmarc.ispnoc.net). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:550:2:61::2fc:100 (lastmx.spamexperts.net). Ask your hosting provider to set one.
    #30
  • !
    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 locksecure.nl ›