fcgroningen.nl

Checked 21 October 2026, 21:15 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:40.92.0.0/15 ip4:51.4.72.0/24 ip4:51.5.72.0/24 ip4:51.5.80.0/27 ip4:51.4.80.0/27 ip4:185.46.182.1 ip4:13.111.0.0/16 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip4:77.94.250.156 ip4:77.94.250.157 ip4:77.94.250.158 ip4:77.94.250.159 ip4:69.72.32.0/20 ip4:167.89.61.143 ip4:166.78.68.0/22 ip4:20.82.87.96/28 ip4:198.245.81.0/24 ip6:2a00:f60::2:156 ip6:2a00:f60::2:157 ip6:2a00:f60::2:158 include:_spf0000000.fcgroningen.nl -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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, ip4:52.100.0.0/14. Check that you really own and send from all of them.
    #27

DMARC

fail

p=none (_dmarc.fcgroningen.nl)

Found

Record
v=DMARC1; p=none; rua=mailto:c18ad04a@in.mailhardener.com
Found at
_dmarc.fcgroningen.nl
External report address
mailto:c18ad04a@in.mailhardener.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:c18ad04a@in.mailhardener.comAggregate report addresses

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:c18ad04a@in.mailhardener.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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

1 mail server

Found

PriorityHostRecordsReverse DNS
0fcgroningen-nl.mail.protection.outlook.comA 52.101.91.159 A 52.101.181.156 A 52.101.103.36 A 52.101.68.27 AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca21::e AAAA 2a01:111:f403:ca48::email-matpr04cu00207.inbound.protection.outlook.com ✓ mail-wa4pr05cu00104.inbound.protection.outlook.com ✓ mail-miypr05cu00104.inbound.protection.outlook.com ✓ mail-db7pr03cu00503.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-matpr04cu00306.inbound.protection.outlook.com ✓ mail-miypr03cu00206.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
fcgroningen-nl.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