DNS & Email Security Report for ns.nl

• A record presentcritical

  1 A record(s) found

• AAAA record presentrecommended

  No AAAA records

• MX records presentrecommended

  1 MX record(s) found

• NS records presentcritical

  6 NS record(s) found

• SOA record presentcritical

  SOA record found

• Multiple nameserversrecommended

  6 nameservers configured ✓

• SOA serial formatinfo

  Serial 1562577016 (valid, managed DNS format)

• SOA timers validinfo

  Refresh: 43200s ✓, Retry: 7200s ✓, Expire: 604800s ✓

• No lame nameserversinfo

  6 NS all responding ✓

• Glue records presentinfo

  No glue needed

• WWW record configuredinfo

  CNAME: ns.nl.edgekey.net

• MX servers have PTR recordsinfo

  8 MX IPs all have PTR records ✓

• MX servers have FCrDNSinfo

  8 MX IPs have forward-confirmed reverse DNS ✓

• DNSSEC signedrecommended

  DNSSEC is enabled ✓

• DNSSEC validation OKcritical

  DNSSEC validates correctly ✓

• NSEC3 RFC 9276 compliantrecommended

  NSEC3 iterations=0, salt=empty — RFC 9276 compliant ✓

• RRSIG signatures validrecommended

  RRSIG signature expires in 2 days — renewal needed

• Modern DNSSEC algorithmoptional

  RSA/SHA-256 (algorithm 8) — acceptable ✓

• DS digest algorithm modernrecommended

  DS digest: SHA-256 — modern ✓

• DNSKEY algorithm secureoptional

  DNSKEY: RSA/SHA-256 — acceptable, consider ECDSA (13) or Ed25519 (15)

• RRSIG TTL saferecommended

  Record TTLs do not exceed RRSIG validity periods ✓

• Chain of trust completecritical

  Complete chain: DNSKEY + DS + RRSIG ✓

• Website reachable via IPv6recommended

  No IPv6 for website. Add AAAA record pointing to your IPv6 address

• Mail servers reachable via IPv6recommended

  1/1 MX server(s) with IPv6 ✓

• Nameservers reachable via IPv6recommended

  6/6 NS server(s) with IPv6 ✓

• SPF record presentcritical

  v=spf1 include:_spf-a.ns.nl include:_spf-b.ns.nl include:spf.protection.outlook.com include:sendgrid.net include:_spf.mail.services.bastion365.net include:servers.mcsv.net exists:%{i}._spf.mta.salesforce.com -all

• SPF syntax validcritical

  SPF syntax is correct ✓

• SPF policy strict (-all)recommended

  SPF uses -all (hard fail) ✓

• DKIM foundrecommended

  DKIM selector: default ✓

• DMARC record presentrecommended

  v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected];

• DMARC policy quarantine or betterrecommended

  DMARC policy: reject ✓

• DMARC policy rejectoptional

  DMARC policy: reject ✓

• BIMI record presentoptional

  No BIMI record. Add TXT at default._bimi with logo URL (requires DMARC p=quarantine+)

• BIMI configuration validoptional

  No BIMI configured

• MTA-STS record presentoptional

  No MTA-STS. Add TXT at _mta-sts and host policy at /.well-known/mta-sts.txt

• MTA-STS policy enforcedoptional

  MTA-STS not configured

• MX records validcritical

  1 MX record(s) ✓

• MX domains use DNSSECrecommended

  1/1 MX domain(s) use DNSSEC ✓

• MX DNSSEC validation OKrecommended

  MX DNSSEC validates correctly ✓

• Mail servers not blacklistedcritical

  1 MX server(s) checked against 16 blacklists - clean ✓

• No critical blacklist listingscritical

  No blacklist listings ✓

• CAA records presentrecommended

  No CAA records. Add CAA record to specify allowed certificate authorities

• CAA policy strictoptional

  CAA not strict. Add CAA 0 issue "letsencrypt.org" (or your CA) to restrict issuance

• TLSA records (DANE)optional

  6 DANE record(s) - configured according to best practices

• DANE configuration validoptional

  DANE records meet best practices ✓

• No sensitive info in TXTcritical

  No sensitive data leaked ✓

• Verification records reviewedinfo

  7 verification records found (Apple, Atlassian, Microsoft 365, Google, MongoDB...). Review these - they reveal your tech stack to attackers. Remove unused service verifications

• HTTPS availablecritical

  HTTPS working (status 200) ✓

• Valid certificatecritical

  Certificate chain is valid and trusted ✓

• HTTP redirects to HTTPScritical

  HTTP automatically redirects to HTTPS ✓

• HSTS enabledrecommended

  HSTS enabled (max-age=31536000) ✓

• HSTS max-age >= 1 yearoptional

  max-age=31536000 (≥1 year) ✓

• X-Frame-Options headerrecommended

  X-Frame-Options: sameorigin ✓

• X-Content-Type-Options headerrecommended

  X-Content-Type-Options: nosniff ✓

• Content-Security-Policy headerrecommended

  Content-Security-Policy configured ✓

• Referrer-Policy headerrecommended

  Referrer-Policy: same-origin ✓

• security.txt presentoptional

  No security.txt. Create /.well-known/security.txt with Contact and Expires fields (RFC 9116)

• security.txt validoptional

  No security.txt configured

• HTTP/3 (QUIC) supportedoptional

  No HTTP/3 support detected No h3 in Alt-Svc header No HTTPS DNS record (type 65) QUIC probe inconclusive (Inconclusive - no QUIC reply (trigger may be dropped or UDP/443 filtered)) — not a negative signal

• QUIC UDP reachableinfo

  QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

• HTTPS DNS record (SVCB)optional

  No HTTPS DNS record (type 65). Add HTTPS record for faster HTTP/3 discovery: ns.nl IN HTTPS 1 . alpn="h3,h2"

Add IPv6 support

Request AAAA records from your hosting provider for your website. IPv6 is becoming increasingly important.

Impact: Makes your website accessible to IPv6-only networks

Add CAA records

Define which Certificate Authorities may issue SSL certificates, for example: "0 issue letsencrypt.org"

Impact: Prevents unauthorized certificate issuance

Review verification TXT records

Your domain has many third-party verification records that reveal your tech stack (Google, Microsoft, Atlassian, etc.). Review each one: 1) Remove records for services no longer used 2) Consider if each service really needs domain verification 3) Use a subdomain for less critical services. This is an information disclosure issue - attackers can map your SaaS footprint.

Impact: Reduces reconnaissance surface and limits attacker knowledge of your infrastructure

Enable HTTP/3 (QUIC)

Enable HTTP/3 for faster page loads and improved connection resilience. Nginx: add "listen 443 quic reuseport;" and "add_header Alt-Svc 'h3=":443"; ma=86400'". Caddy: HTTP/3 is enabled by default. Cloudflare: Enable under Speed → Protocol Optimization. Also add an HTTPS DNS record: example.com IN HTTPS 1 . alpn="h3,h2" Ensure UDP port 443 is open in your firewall (QUIC uses UDP, not TCP).

Impact: Faster page loads (0-RTT), better mobile performance, and connection migration between networks