redlights.be

Checked 22 October 2026, 07:02 UTC · via 8.8.8.8
!Passed with warnings
27 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:83.217.72.40 ip4:35.210.16.233 ip4:35.210.231.122 ip4:35.210.90.55 ip4:34.140.250.124 ip6:2a00:1c98:10:19::10 include:_spf.google.com include:spf.protection.outlook.com include:email.freshdesk.com ~all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 9 of 10 DNS lookups #2
    SPF record needs 9 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

warn

p=quarantine (_dmarc.redlights.be)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:webmaster@redlights.be; ruf=mailto:webmaster@redlights.be; fo=1;
Found at
_dmarc.redlights.be
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:webmaster@redlights.beAggregate report addresses
rufmailto:webmaster@redlights.beFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:webmaster@redlights.be
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

pass

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
65115, 15380
Signatures valid until
11 November 2026, 10:01 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-11 #21
    DNSKEY signatures are valid until 2026-11-11T10:01:13Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0redlights-be.mail.protection.outlook.comA 52.101.91.162 A 52.101.181.156 A 52.101.68.21 A 52.101.103.39 AAAA 2a01:111:f403:ca04::e AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca04::b AAAA 2a01:111:f403:ca04::9mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-wa4pr05cu00104.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-dbbpr03cu00103.inbound.protection.outlook.com ✓ mail-db7pr03cu00601.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
redlights-be.mail.protection.outlook.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