SurfaceMap › t › timeweb.com

timeweb.com

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

Domain & DNS

fail

27 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers !SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns4.timeweb.org (139.45.249.139): read udp 46.225.38.91:44573->139.45.249.139:53: i/o timeout.
    #14
  • !
    Unusual SOA timers
    SOA · expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 8h, retry 2h, expire 3d, negative TTL 5m.
    #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 timeweb.com ›

Mail

warn

25 passed 4 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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@timeweb.ru (needs timeweb.com._report._dmarc.timeweb.ru). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 timeweb.com ›