galaxyclub.nl

SPF record published

Found

Record

v=spf1 a mx ptr ip4:141.138.168.0/21 ip6:ffff:ac68:f3b7::/48 ip6:ffff:8d8a:a873::/48 ip4:195.211.72.0/21 ~all

DNS lookups

3 of 10

Void lookups

0 of 2

Checks

• !

  Uses deprecated ptr mechanism

  The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.

  #1
• ✓ 3 of 10 DNS lookups #2

  SPF record needs 3 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.

No keys found under the checked selectors

Found

Selectors

None found

_domainkey

NOERROR

Checks

• !

  No key under common selectors

  The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

  #7

Signed, but no DS at parent

Found

DNSKEY records

Yes (2)

DS at parent

No

Algorithms

ECDSAP256SHA256 (13)

Key tags

2371, 34505

Signatures valid until

15 December 2026, 20:03 UTC

Checks

• !

  Signed, but no DS at parent

  The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

  #8
• ✓ Signatures valid until 2026-12-15 #21

  DNSKEY signatures are valid until 2026-12-15T20:03:27Z.

1 mail server

Found

Checks

• ✓ 1 MX record #9

  Found 1 MX records for this domain.
• ✓ All hosts resolve #10

  All MX records resolve to valid IP addresses.
• !

  Hosts without IPv6

  The following MX hosts could not be resolved to IPv6 addresses: mail.galaxyclub.nl

  #11
• !

  Single MX host, no backup

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

  #12
• ✓ At most 5 MX records #13

  Found 1 MX records, which is within the recommended range (1-5).
• ✓ 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 1 MX address have a PTR record that resolves back to them.

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

Found

DANE (TLSA records)

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