oray.com

Checked 22 October 2026, 10:10 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 3 failed 4 info

Registration

info

.com generic · Shanghai Best Oray Information S&T Co., Ltd. · expires 2029-06-24

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Shanghai Best Oray Information S&T Co., Ltd.
Registered
24 June 2001
Last changed
17 March 2026
Expires
24 June 2029
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns1.oray.com, ns2.oray.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2029-06-24 #3
    The registration is valid until 2029-06-24 (976 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.oray.com, ns2.oray.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.oray.com, ns2.oray.com
NS in the zone
ns1.oray.com, ns2.oray.com
NameserverAddressesNetwork (AS)Glue
ns1.oray.com81.71.145.128 120.77.155.64 118.31.42.180 123.207.112.38AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN118.31.42.180 120.77.155.64 123.207.112.38 81.71.145.128
ns2.oray.com112.74.164.167 193.112.84.125 120.55.55.35 123.207.104.105AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN112.74.164.167 120.55.55.35 123.207.104.105 193.112.84.125

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.oray.com, ns2.oray.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.oray.com, ns2.oray.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 8 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 4 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 4 addresses.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

7 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.oray.com 81.71.145.128NOERROR, 205 ms, authoritativenono / yesrefused-
ns1.oray.com 120.77.155.64NOERROR, 202 ms, authoritativenono / yesrefused-
ns1.oray.com 118.31.42.180NOERROR, 200 ms, authoritativenono / yesrefused-
ns1.oray.com 123.207.112.38NOERROR, 197 ms, authoritativenono / yesrefused-
ns2.oray.com 112.74.164.167NOERROR, 205 ms, authoritativenono / yesrefused-
ns2.oray.com 193.112.84.125NOERROR, 205 ms, authoritativenono / yesrefused-
ns2.oray.com 120.55.55.35NOERROR, 227 ms, authoritativenono / yesrefused-
ns2.oray.com 123.207.104.105no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    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
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    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
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

fail

serial 4304043 · primary peanutmail.newpeanut.idc

Found

Primary (MNAME)
peanutmail.newpeanut.idc
Contact (RNAME)
domain_admin\@oray.cn
Serial
4304043
Refresh / retry
900 s / 600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.oray.com (81.71.145.128)4304043
ns1.oray.com (120.77.155.64)4304043
ns1.oray.com (118.31.42.180)4304043
ns1.oray.com (123.207.112.38)4304043
ns2.oray.com (112.74.164.167)4304043
ns2.oray.com (193.112.84.125)4304043
ns2.oray.com (120.55.55.35)4304043

Checks

  • ✓ Serial 4304043 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    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
  • i
    Hidden master (not resolvable)
    The primary nameserver peanutmail.newpeanut.idc is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✗
    Invalid contact address
    The SOA RNAME "domain_admin\\@oray.cn" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✓ Counter serial #26
    The serial 4304043 is a plain counter.

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

warn

13 records at the apex

Found

Read from
81.71.145.128:53
TypeValueTTL
SOApeanutmail.newpeanut.idc. domain_admin\@oray.cn. 4304043 900 600 86400 3600300
NSns2.oray.com.300
NSns1.oray.com.300
A47.110.142.4360
MX5 mxbiz1.qq.com.60
MX10 mxbiz2.qq.com.60
TXT"_7bj30qt37enf908zjp0i5h7wd2ee8mo"60
TXT"google-site-verification=3y1kIq0EeuWOX1H75bxXhESnypQxVzvmq7lJYck_xsE"60
TXT"v=spf1 include:spf.mail.qq.com -all"60
CAA0 issuewild "digicert.com"60
CAA0 issuewild "sectigo.com"60
CAA0 issue "digicert.com"60
CAA0 issue "sectigo.com"60

Checks

  • !
    Very low TTLs
    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
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, sectigo.com.