themehorse.com

Checked 22 October 2026, 11:02 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 7 info

Registration

info

.com generic · NameCheap, Inc. · expires 2027-09-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
3 September 2012
Last changed
25 August 2026
Expires
3 September 2027
Status
client transfer prohibited
Registry nameservers
ns.liquidweb.com, ns1.liquidweb.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-09-03 #3
    The registration is valid until 2027-09-03 (315 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns.liquidweb.com, ns1.liquidweb.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns.liquidweb.com, ns1.liquidweb.com
NS in the zone
ns.liquidweb.com, ns1.liquidweb.com
NameserverAddressesNetwork (AS)Glue
ns.liquidweb.com69.16.222.254 2607:fad0:0:8917::aAS32244 LIQUIDWEB - Liquid Web, L.L.C, US AS32244 LIQUIDWEB - Liquid Web, L.L.C, US69.16.222.254
ns1.liquidweb.com69.16.223.254 2607:fad0:0:8927::aAS32244 LIQUIDWEB - Liquid Web, L.L.C, US AS32244 LIQUIDWEB - Liquid Web, L.L.C, US69.16.223.254

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.liquidweb.com, ns1.liquidweb.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns.liquidweb.com (glue 69.16.222.254, zone 69.16.222.254, 2607:fad0:0:8917::a); ns1.liquidweb.com (glue 69.16.223.254, zone 69.16.223.254, 2607:fad0:0:8927::a). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2607:fad0::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS32244 (LIQUIDWEB - Liquid Web, L.L.C, US): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.liquidweb.com 69.16.222.254NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns.liquidweb.com 2607:fad0:0:8917::aNOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.liquidweb.com 69.16.223.254NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.liquidweb.com 2607:fad0:0:8927::aNOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2024062101 · primary ns.liquidweb.com

Found

Primary (MNAME)
ns.liquidweb.com
Contact (RNAME)
admin.liquidweb.com
Serial
2024062101
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
14400 s

Serial per nameserver

NameserverSerial
ns.liquidweb.com (69.16.222.254)2024062101
ns.liquidweb.com (2607:fad0:0:8917::a)2024062101
ns1.liquidweb.com (69.16.223.254)2024062101
ns1.liquidweb.com (2607:fad0:0:8927::a)2024062101

Checks

  • ✓ Serial 2024062101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 4h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.liquidweb.com is one of the listed nameservers.
  • ✓ Contact admin@liquidweb.com #25
    The SOA RNAME admin.liquidweb.com means admin@liquidweb.com.
  • ✓ Date-based serial #26
    The serial 2024062101 follows the YYYYMMDDnn convention (2024-06-21).

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

10 records at the apex

Found

Read from
69.16.222.254:53
TypeValueTTL
SOAns.liquidweb.com. admin.liquidweb.com. 2024062101 86400 7200 3600000 144003600
NSns.liquidweb.com.3600
NSns1.liquidweb.com.3600
A209.59.129.453600
MX5 ALT1.ASPMX.L.GOOGLE.com.3600
MX10 ASPMX2.GOOGLEMAIL.com.3600
MX1 ASPMX.L.GOOGLE.com.3600
MX10 ASPMX3.GOOGLEMAIL.com.3600
MX5 ALT2.ASPMX.L.GOOGLE.com.3600
TXT"v=spf1 include:_spf.google.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, 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.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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