polestar.com

SPF record published

Found

Record

v=spf1 ip4:3.7.25.40/29 ip4:3.25.47.0/29 ip4:3.120.181.200/29 ip4:3.222.0.24/29 ip4:13.127.153.86 ip4:13.127.210.61 ip4:23.253.182.0/23 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:50.31.32.0/19 ip4:51.4.72.0/24 ip4:51.4.80.0/27 include:spf1.polestar.com ~all

DNS lookups

10 of 10

Void lookups

0 of 2

Checks

• ✓ No deprecated ptr mechanism #1

  No ptr mechanism found in SPF record.
• ✓ 10 of 10 DNS lookups #2

  SPF record needs 10 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.
• !

  Broad IP ranges

  These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15. Check that you really own and send from all of them.

  #27

Selectors: k1, selector1, s1, s2

Found

Selectors

k1, selector1, s1, s2

_domainkey

NOERROR

Checks

• ✓ Keys found: k1, selector1, s1, s2 #7

  DKIM keys found for this domain with selectors: k1, selector1, s1, s2
• !

  1024-bit DKIM key

  1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

  #23
• ✓ No problematic flags #24

  No keys in test mode, revoked, or limited to SHA-1.

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

29 November 2026, 05:45 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-11-29 #21

  DNSKEY signatures are valid until 2026-11-29T05:45:37Z.

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: polestar-com.mail.protection.outlook.com

  #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 4 MX addresss have a PTR record that resolves back to them.

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

Found

TLS-RPT record

v=TLSRPTv1; rua=mailto:rafy0hu6@tls.eu.dmarcadvisor.com

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
• ✓ Reports enabled #35

  TLS reports are sent to: mailto:rafy0hu6@tls.eu.dmarcadvisor.com
• 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