SurfaceMap › p › palarch.nl

palarch.nl

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

Domain & DNS

error

20 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC !Records

Problems

  • !
    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
  • !
    Very high TTLs
    Records · These records have a TTL above 7d, so changes take very long to reach everyone: NS (500h). The NS TTL at the parent is 1h and in the zone 500h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for palarch.nl ›

Mail

fail

18 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    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: mx1-hosting.jellyfish.systems, mx2-hosting.jellyfish.systems, mx3-hosting.jellyfish.systems
    #11
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 162.255.118.28 -> oxse3a.privateemail.com, 162.255.118.29 -> oxse2b.privateemail.com.
    #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 palarch.nl ›