SurfaceMap › t › tokengroup.com

tokengroup.com

Checked 2026-10-22 11:10 UTC · first added 2026-10-21
!Passed with warnings Score 73 of 100

Domain & DNS

warn

21 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2020091322 on dns7.hichina.com (139.224.142.123); 2026081813 on dns8.hichina.com (120.76.107.44); 2026082509 on dns8.hichina.com (139.224.142.114); 2026082616 on dns7.hichina.com (47.118.199.213), dns7.hichina.com (39.96.153.43), dns7.hichina.com (47.118.199.203), dns7.hichina.com (39.96.153.63), dns7.hichina.com (120.76.107.43), dns8.hichina.com (47.118.199.214), dns8.hichina.com (39.96.153.44), dns8.hichina.com (47.118.199.204), dns8.hichina.com (2408:4009:501::16); 2026082617 on dns7.hichina.com (120.76.107.63), dns7.hichina.com (2408:4009:501::15), dns8.hichina.com (39.96.153.54), dns8.hichina.com (120.76.107.54); 2026082709 on dns7.hichina.com (139.224.142.113), dns8.hichina.com (139.224.142.124). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #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 tokengroup.com ›

Mail

warn

23 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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: mx1.qiye.aliyun.com, mx2.qiye.aliyun.com, mx3.qiye.aliyun.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (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: 47.246.167.188 (mx1.qiye.aliyun.com), 47.246.137.47 (mx3.qiye.aliyun.com). 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 tokengroup.com ›