openresty.com

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

Registration

info

.com generic · Squarespace Domains II LLC · expires 2027-04-24

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Squarespace Domains II LLC
Registered
24 April 2008
Last changed
9 April 2026
Expires
24 April 2027
Status
client delete prohibited, client transfer prohibited
Registry nameservers
n1.openresty.com, n2.openresty.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 2027-04-24 #3
    The registration is valid until 2027-04-24 (183 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

n1.openresty.com, n2.openresty.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
n1.openresty.com, n2.openresty.com
NS in the zone
n1.openresty.com, n2.openresty.com
NameserverAddressesNetwork (AS)Glue
n1.openresty.com52.11.111.175AS16509 AMAZON-02 - Amazon.com, Inc., US52.11.111.175
n2.openresty.com52.220.196.30AS16509 AMAZON-02 - Amazon.com, Inc., US52.220.196.30

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: n1.openresty.com, n2.openresty.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: n1.openresty.com, n2.openresty.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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
n1.openresty.com 52.11.111.175NOERROR, 173 ms, authoritativenono / norefused-
n2.openresty.com 52.220.196.30NOERROR, 239 ms, authoritativenoyes / norefused-

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✓ 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: n1.openresty.com (52.11.111.175): dial tcp 52.11.111.175:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: n1.openresty.com (52.11.111.175), n2.openresty.com (52.220.196.30).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1792642420 · primary n1.openresty.com

Found

Primary (MNAME)
n1.openresty.com
Contact (RNAME)
admin\\.openresty.com
Serial
1792642420
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
n1.openresty.com (52.11.111.175)1792642420
n2.openresty.com (52.220.196.30)1792642420

Checks

  • ✓ Serial 1792642420 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver n1.openresty.com is one of the listed nameservers.
  • ✓ Contact admin\\@openresty.com #25
    The SOA RNAME admin\\.openresty.com means admin\\@openresty.com.
  • ✓ Timestamp serial #26
    The serial 1792642420 is a Unix timestamp (2026-10-22 04:13 UTC).

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

info

14 records at the apex

Found

Read from
52.11.111.175:53
TypeValueTTL
SOAn2.openresty.com. admin\\.openresty.com. 1792642420 10800 3600 604800 36003600
NSn1.openresty.com.3600
NSn2.openresty.com.3600
A3.74.86.167300
MX5 alt1.aspmx.l.google.com.18000
MX10 aspmx2.googlemail.com.18000
MX10 aspmx3.googlemail.com.18000
MX1 aspmx.l.google.com.18000
MX5 alt2.aspmx.l.google.com.18000
TXT"google-site-verification=aAbFX76ug8gEpDSsP7j--VE1avRWTgBCeW4tIHZmTGY"300
TXT"v=spf1 include:_spf.google.com ~all"300
TXT"google-site-verification=MuK4tp25mtyYrJoEupvwIJbWqx6PGsx2078nSl7ksOg"300
TXT"google-site-verification=80WBuarroo-dWHVrPta5Qi21NZk7Xk1QKtfL7iRwh50"300
TXT"google-site-verification=dOK0b9pb7SNyZopFTuTYyoRrdwLRIx9DVpexFTpa2A0"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5h, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35