SurfaceMap › s › solo.be

solo.be

Checked 2026-10-22 07:11 UTC · first added 2026-10-21
✗Problems found Score 69 of 100

Domain & DNS

fail

21 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.iptwins.net (193.70.18.204): read tcp 46.225.38.91:41022->193.70.18.204:53: i/o timeout; ns3.iptwins.com (144.217.70.141): read tcp 46.225.38.91:41790->144.217.70.141:53: i/o timeout; ns3.iptwins.com (2607:5300:203:28d::): read tcp [2a01:4f8:1c1c:eebf::1]:58432->[2607:5300:203:28d::]:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 4d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 30d, negative TTL 4d.
    #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 solo.be ›

Mail

warn

22 passed 5 warn 0 failed

Areas

✓SPF ✓DMARC iDKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    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: mail.dms.unileverservices.com
    #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
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 20.115.101.171 (mail.dms.unileverservices.com). 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 solo.be ›