SurfaceMap › p › philadelphia.nl

philadelphia.nl

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

Domain & DNS

error

29 passed 1 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✓Delegation !Nameservers ✓SOA ✓DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: nsauth1.bit.nl: "PowerDNS Authoritative Server 4.9.15 (built May 11 2026 09:10:06 by root@localhost)"; nsauth2.bit.nl: "PowerDNS Authoritative Server 4.9.15 (built May 11 2026 09:10:06 by root@localhost)"; nsauth3.bitnl.eu: "PowerDNS Authoritative Server 4.9.11 (built Oct 15 2025 10:16:15 by root@localhost)". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for philadelphia.nl ›

Mail

warn

24 passed 6 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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Applies to 10% of mail
    DMARC · DMARC policy only applies to 10% of failing mail (pct=10). Raise pct to 100 once you are confident in your setup.
    #18
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (1024 bits), selector2 (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:support.security.nl@axians.com (needs philadelphia.nl._report._dmarc.axians.com). 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 philadelphia.nl ›