themeholy.com

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

Registration

info

.com generic · Purple IT Ltd · expires 2027-03-29

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Purple IT Ltd
Registered
29 March 2023
Last changed
18 June 2025
Expires
29 March 2027
Status
client transfer prohibited
Registry nameservers
ns1.exonhost.com, ns2.exonhost.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-03-29 #3
    The registration is valid until 2027-03-29 (158 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

fail

ns1.exonhost.com, ns2.exonhost.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.exonhost.com, ns2.exonhost.com
NS in the zone
ns1.cprapid.com, ns2.cprapid.com
NameserverAddressesNetwork (AS)Glue
ns1.cprapid.com (zone only)(does not resolve)-
ns1.exonhost.com (parent only)104.223.14.195AS36352 AS-COLOCROSSING - HostPapa, US104.223.14.195
ns2.cprapid.com (zone only)(does not resolve)-
ns2.exonhost.com (parent only)69.164.244.253AS19318 IS-AS-1 - Interserver, Inc, US69.164.244.253

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.exonhost.com, ns2.exonhost.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.exonhost.com, ns2.exonhost.com; only in the zone: ns1.cprapid.com, ns2.cprapid.com. ns1.exonhost.com, ns2.exonhost.com report NS ns1.cprapid.com ns2.cprapid.com.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns1.cprapid.com, ns2.cprapid.com.
    #9
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS19318 (IS-AS-1 - Interserver, Inc, US): 1 address; AS36352 (AS-COLOCROSSING - HostPapa, US): 1 address.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.exonhost.com, ns2.exonhost.com.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.exonhost.com 104.223.14.195NOERROR, 147 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)
ns2.exonhost.com 69.164.244.253NOERROR, 87 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.exonhost.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; ns2.exonhost.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". Hide or replace the version string.
    #17
  • ✓ 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 2026102202 · primary ns1.cprapid.com

Found

Primary (MNAME)
ns1.cprapid.com
Contact (RNAME)
notify.exonhost.gmail.com
Serial
2026102202
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.exonhost.com (104.223.14.195)2026102202
ns2.exonhost.com (69.164.244.253)2026102202

Checks

  • ✓ Serial 2026102202 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.cprapid.com is one of the listed nameservers.
  • ✓ Contact notify@exonhost.gmail.com #25
    The SOA RNAME notify.exonhost.gmail.com means notify@exonhost.gmail.com.
  • ✓ Date-based serial #26
    The serial 2026102202 follows the YYYYMMDDnn convention (2026-10-22).

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

6 records at the apex

Found

Read from
104.223.14.195:53
TypeValueTTL
SOAns1.cprapid.com. notify.exonhost.gmail.com. 2026102202 3600 1800 1209600 8640086400
NSns2.cprapid.com.86400
NSns1.cprapid.com.86400
A51.81.154.16314400
MX0 themeholy.com.14400
TXT"v=spf1 ip4:51.81.154.163 +a +mx +ip4:23.239.118.6 ~all"14400

Checks

  • ✓ TTLs within range #32
    TTLs: A 4h, MX 4h, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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