vgc.be

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

SPF

warn

SPF record published

Found

Record
v=spf1 a mx ip4:185.111.196.197 ip4:193.30.110.0/16 ip4:3.123.206.219 ip4:3.68.129.51 ip4:13.36.253.151 include:spf.protection.outlook.com include:servers.mcsv.net include:sendgrid.net include:_spf.level27.be ?all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 7 of 10 DNS lookups #2
    SPF record needs 7 DNS lookups (limit is 10).
  • !
    Ends with ?all (neutral)
    SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • ✓ 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.vgc.be)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarcreports@vgc.be
Found at
_dmarc.vgc.be
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarcreports@vgc.beAggregate report addresses

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:dmarcreports@vgc.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

warn

Selectors: k1, selector1, selector2, s1, s2

Found

Selectors
k1, selector1, selector2, s1, s2
_domainkey
NXDOMAIN
SelectorKeyFlags
k1RSA 1024 bits
selector1RSA 1024 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: k1, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: k1, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (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.

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
5argos.vgc.beA 195.244.180.2jacqmain.axs.vgc.be ✓
10rp.vgc.beA 195.244.180.4no PTR
30mx2.vgc.beA 91.183.140.226mx2.vgc.be ✓
50vgc-be.mail.protection.outlook.comA 52.101.91.159 A 52.101.91.156 A 52.101.73.145 A 52.101.73.126 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca21::8 AAAA 2a01:111:f403:ca09::22mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-maspr04cu00104.inbound.protection.outlook.com ✓ mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.inbound.protection.outlook.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: argos.vgc.be, rp.vgc.be, mx2.vgc.be
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 195.244.180.4 (rp.vgc.be). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
argos.vgc.benone-
rp.vgc.benone-
mx2.vgc.benone-
vgc-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