SurfaceMap › t › techpulse.be

techpulse.be

Checked 2026-10-22 07:12 UTC · first added 2026-10-21

✗Problems found Score 62 of 100

Domain & DNS

warn

25 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC iRecords

Problems

!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: elma.ns.cloudflare.com: "2026.10.2"; ram.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.

#17

Recent checks

!

Full report

Domain & DNS report for techpulse.be ›

Mail

fail

18 passed 5 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
✗

Syntax errors

SPF · Receivers reject the whole SPF record (permerror) because of: unknown mechanism "ipv4:104.248.91.209".

#25
!

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
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mx.mailprotect.be

#11
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

No aggregate reports (rua)

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
!

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 techpulse.be ›