xboxworld.nl

Checked 21 October 2026, 21:27 UTC · via 8.8.8.8
✗Problems found
14 passed 5 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com a:server5.xboxworld.nl ~all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    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

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.xboxworld.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

7 mail servers

Found

PriorityHostRecordsReverse DNS
10aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
20alt1.aspmx.l.google.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1brd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
20alt2.aspmx.l.google.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1byulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
30aspmx2.l.googlemail.com(does not resolve)
30aspmx3.l.googlemail.com(does not resolve)
30aspmx4.l.googlemail.com(does not resolve)
30aspmx5.l.googlemail.com(does not resolve)

Checks

  • ✓ 7 MX records #9
    Found 7 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: aspmx2.l.googlemail.com, aspmx3.l.googlemail.com, aspmx4.l.googlemail.com, aspmx5.l.googlemail.com
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: aspmx2.l.googlemail.com, aspmx3.l.googlemail.com, aspmx4.l.googlemail.com, aspmx5.l.googlemail.com
    #11
  • ✓ Redundant MX hosts #12
    Found 7 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 7 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
aspmx2.l.googlemail.comnone-
aspmx3.l.googlemail.comnone-
aspmx4.l.googlemail.comnone-
aspmx5.l.googlemail.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38