SurfaceMap › v › vk.com

vk.com

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

Domain & DNS

fail

19 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.vk.com (2a00:bdc0:ff:1::2): read udp [2a01:4f8:1c1c:eebf::1]:57832->[2a00:bdc0:ff:1::2]:53: i/o timeout; ns2.vk.com (2a00:bdc0:ff:2::2): read udp [2a01:4f8:1c1c:eebf::1]:50132->[2a00:bdc0:ff:2::2]:53: i/o timeout; ns3.vk.com (2a00:bdc0:ff:3::2): read udp [2a01:4f8:1c1c:eebf::1]:58265->[2a00:bdc0:ff:3::2]:53: i/o timeout; ns4.vk.com (2a00:bdc0:ff:4::2): read udp [2a01:4f8:1c1c:eebf::1]:37048->[2a00:bdc0:ff:4::2]:53: i/o timeout.
    #14
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.vk.com (glue 87.240.131.131, zone 87.240.131.131, 2a00:bdc0:ff:1::2); ns2.vk.com (glue 95.213.21.21, zone 95.213.21.21, 2a00:bdc0:ff:2::2); ns3.vk.com (glue 93.186.238.238, zone 93.186.238.238, 2a00:bdc0:ff:3::2); ns4.vk.com (glue 87.240.136.136, zone 87.240.136.136, 2a00:bdc0:ff:4::2). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 7d, negative TTL 15m.
    #23
  • !
    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 vk.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    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: mxs.mail.ru
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 vk.com ›