SurfaceMap › v › vgc.be

vgc.be

Checked 2026-10-22 07:21 UTC · first added 2026-10-21
✗Problems found Score 54 of 100

Domain & DNS

fail

19 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: argos.kasterlinden.be (195.244.184.74): dial tcp 195.244.184.74:53: i/o timeout; argos.vgc.be (195.244.180.2): dial tcp 195.244.180.2:53: connect: connection refused; guard.axs.vgc.be (195.244.180.4): dial tcp 195.244.180.4:53: connect: connection refused; hermes.vgc.be (91.183.140.230): dial tcp 91.183.140.230:53: connect: connection refused; nl.argos.kasterlinden.be (195.244.184.74): dial tcp 195.244.184.74:53: i/o timeout.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: argos.kasterlinden.be, guard.axs.vgc.be. argos.kasterlinden.be, argos.vgc.be, guard.axs.vgc.be, hermes.vgc.be, nl.argos.kasterlinden.be report NS argos.kasterlinden.be argos.vgc.be guard.axs.vgc.be hermes.vgc.be nl.argos.kasterlinden.be.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: hermes.vgc.be (glue 195.244.180.3, zone 91.183.140.230). Update the glue at your registrar.
    #8
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: argos.kasterlinden.be (195.244.184.74), argos.vgc.be (195.244.180.2), guard.axs.vgc.be (195.244.180.4), hermes.vgc.be (91.183.140.230), nl.argos.kasterlinden.be (195.244.184.74).
    #20
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for vgc.be ›

Mail

warn

22 passed 7 warn 0 failed

Areas

!SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: argos.vgc.be, rp.vgc.be, mx2.vgc.be
    #11
  • !
    1024-bit DKIM key
    DKIM · 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
  • !
    Addresses without reverse DNS
    MX · 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
  • !
    Not configured
    TLS · 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

Recent checks

!

Full report

Mail report for vgc.be ›