wonderclub.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 71 days left27 years oldTranco #99712

One re-check per domain each UTC day.

90

wonderclub.com was registered on 10 Mar 1999 via DNC Holdings, Inc. and the registry expiry is 10 Mar 2034. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/wonderclub.com.

wonderclub.com publishes 2 nameservers. DNSSEC is not signed.

wonderclub.com has 2 IPv4 addresses (172.66.40.108, 172.66.43.148) and 2 IPv6 addresses (2606:4700:3108::ac42:286c, 2606:4700:3108::ac42:2b94). The geolocation database places 172.66.40.108 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 71 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, Cloudflare Browser Insights, Google Hosted Libraries, HSTS, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache and jQuery. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for wonderclub.com in the checks that ran.

Domain · RDAP/WHOIS

wonderclub.com was registered on 10 Mar 1999 via DNC Holdings, Inc.. The registry returned 3 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/wonderclub.com.

Registeredsince 10 Mar 1999
Created10 March 1999
Updated9 March 2026
Expires10 March 2034
RegistrarDNC Holdings, Inc.
Statusclient delete prohibited, client transfer prohibited, client update prohibited
Nameserversdarwin.ns.cloudflare.com, zara.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/wonderclub.com

wonderclub.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.

wonderclub.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

wonderclub.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.

Nameserver darwin.ns.cloudflare.com is published for wonderclub.com in the registration record from https://rdap.verisign.com/com/v1/domain/wonderclub.com.

Nameserver zara.ns.cloudflare.com is published for wonderclub.com in the registration record from https://rdap.verisign.com/com/v1/domain/wonderclub.com.

DNS

wonderclub.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A172.66.40.108, 172.66.43.148
AAAA2606:4700:3108::ac42:286c, 2606:4700:3108::ac42:2b94
NSdarwin.ns.cloudflare.com, zara.ns.cloudflare.com
MXmail.wonderclub.com (10)
SPFpresent
DMARCpresent
CAAissue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at wonderclub.com is "v=spf1 +mx +a +ip4:51.222.240.34 include:amazonses.com ~all".

The DMARC text record at _dmarc.wonderclub.com is "v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]".

IPv4 address 172.66.40.108 answers for wonderclub.com at resolver 1.1.1.1:53.

IPv4 address 172.66.43.148 answers for wonderclub.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3108::ac42:286c answers for wonderclub.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3108::ac42:2b94 answers for wonderclub.com at resolver 1.1.1.1:53.

Mail exchanger mail.wonderclub.com has preference 10.

Hosting and geo

wonderclub.com is placed in Toronto, Canada by the local geolocation database (db-ip).

Address172.66.40.108
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for wonderclub.com is valid, with 71 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectwonderclub.com
Valid from12 October 2026
Valid until11 January 2027
Days left71
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.wonderclub.com, wonderclub.com.

Tech stack

Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • Cloudflare Browser Insights · Analytics, RUM
  • Google Hosted Libraries · CDN
  • HSTS · Security
  • HTTP/3 · Miscellaneous
  • LiteSpeed · Web servers
  • LiteSpeed Cache · Caching, WordPress plugins
  • Litespeed Cache · Caching, WordPress plugins
  • jQuery · JavaScript libraries

Cloudflare is filed under CDN.

Cloudflare Browser Insights is filed under Analytics, RUM.

Google Hosted Libraries is filed under CDN.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

LiteSpeed is filed under Web servers.

LiteSpeed Cache is filed under Caching, WordPress plugins.

Litespeed Cache is filed under Caching, WordPress plugins.

jQuery is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 402 ms. The target title is 61 characters and the page has 1 H1 heading.

Status200
TTFB402 ms
Title length61 no
Quoted title"Magazine Back Issues & Digital Magazines Archive | WonderClub"
Meta description"Shop WonderClub's massive archive of magazine back issues in digital PDF format. Browse thousands of titles including Penthouse, comics, books, and posters. Instant download available." yes
H1 count1
HSTSyes yes
CSPno
X-Frame-OptionsSAMEORIGIN
Robots metaindex, follow
Canonicalhttps://wonderclub.com/
Languageen
Links15
Images2
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for wonderclub.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

First checked on 30 October 2026; changes will appear here.

Questions

Is wonderclub.com safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts wonderclub.com?

wonderclub.com is placed in Toronto, Canada.

When does wonderclub.com expire?

wonderclub.com expires on 10 March 2034 according to https://rdap.verisign.com/com/v1/domain/wonderclub.com.

Who owns wonderclub.com?

The registry did not return a person or a company for wonderclub.com. RDAP often redacts the registrant. The registrar on file is DNC Holdings, Inc..

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/wonderclub.com at 2026-10-30T14:20:15Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:20:15Z
  • TLS source tls:443 at 2026-10-30T14:20:15Z
  • HTTP source https://wonderclub.com/ at 2026-10-30T14:20:15Z
  • Tech source wappalyzergo at 2026-10-30T14:20:15Z
  • Geo source db-ip at 2026-10-30T14:20:15Z
  • Safety source family DNS and local lists at 2026-10-30T14:20:15Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com DNC Holdings, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.