SurfaceMap › h › hoyoverse.com

hoyoverse.com

Checked 2026-10-22 09:13 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

warn

22 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.14.17, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 220.196.136.52, 2402:4e00:1470:2::f, 35.165.107.227, zone 163.177.5.52, 1.12.14.17, 1.12.0.18, 1.12.0.17, 13.37.58.163, 15.160.102.38, 18.134.75.163, 162.62.49.74, 1.12.14.18, 240d:c000:3011::10); ns4.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.16, 1.12.14.19, 117.135.128.152, 124.64.205.152, 13.37.58.163, 2402:4e00:111:fff::8, 49.7.107.152, zone 1.12.0.16, 13.48.202.4, 18.194.2.137, 63.34.1.181, 1.12.14.16, 1.12.0.19, 162.62.49.12, 1.12.14.19, 240d:c000:3011::f). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns3.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #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 hoyoverse.com ›

Mail

fail

23 passed 5 warn 1 failed

Areas

✓SPF !DMARC ✗DKIM !DNSSEC !MX !TLS ✓BIMI

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.hoyoverse.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (hoyoverse-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (hoyoverse-com.mail.protection.outlook.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 hoyoverse.com ›