SurfaceMap › o › oray.com

oray.com

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

Domain & DNS

fail

20 passed 4 warn 3 failed

Areas

iRegistration !Delegation ✗Nameservers ✗SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns2.oray.com (123.207.104.105): read udp 46.225.38.91:56780->123.207.104.105:53: i/o timeout.
    #14
  • ✗
    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: ns1.oray.com (81.71.145.128): dial tcp 81.71.145.128:53: i/o timeout; ns1.oray.com (120.77.155.64): dial tcp 120.77.155.64:53: i/o timeout; ns1.oray.com (118.31.42.180): dial tcp 118.31.42.180:53: i/o timeout; ns1.oray.com (123.207.112.38): dial tcp 123.207.112.38:53: i/o timeout; ns2.oray.com (112.74.164.167): dial tcp 112.74.164.167:53: i/o timeout; ns2.oray.com (193.112.84.125): dial tcp 193.112.84.125:53: i/o timeout; ns2.oray.com (120.55.55.35): dial tcp 120.55.55.35:53: i/o timeout.
    #19
  • ✗
    Invalid contact address
    SOA · The SOA RNAME "domain_admin\\@oray.cn" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 15m, retry 10m, expire 1d, negative TTL 1h.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for oray.com ›

Mail

warn

19 passed 7 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
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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: mxbiz1.qq.com, mxbiz2.qq.com
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.3 (mxbiz1.qq.com), 103.86.78.2 (mxbiz1.qq.com), 43.154.252.16 (mxbiz2.qq.com), 43.154.252.202 (mxbiz2.qq.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 oray.com ›