masaladesi.club

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

HTTP 403Family DNS blockedSSL: 80 days left7 years old

One re-check per domain each UTC day.

50

masaladesi.club was registered on 30 Sep 2019 via GoDaddy.com, LLC and the registry expiry is 30 Sep 2027. WHOIS data came from RDAP at https://rdap.nic.club/domain/masaladesi.club.

masaladesi.club publishes 2 nameservers. DNSSEC is not signed.

masaladesi.club has 2 IPv4 addresses (104.21.64.34, 172.67.175.154) and 2 IPv6 addresses (2606:4700:3033::6815:4022, 2606:4700:3037::ac43:af9a). The geolocation database places 104.21.64.34 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 80 days left (TLS 1.3).

Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

masaladesi.club was registered on 30 Sep 2019 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.nic.club/domain/masaladesi.club.

Registeredsince 30 Sep 2019
Created30 September 2019
Updated28 September 2026
Expires30 September 2027
RegistrarGoDaddy.com, LLC
Statusclient transfer prohibited, client renew prohibited, client update prohibited, client delete prohibited
Nameserversjobs.ns.cloudflare.com, lila.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.nic.club/domain/masaladesi.club

masaladesi.club 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.

masaladesi.club carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.

masaladesi.club 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.

masaladesi.club 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.

Nameserver jobs.ns.cloudflare.com is published for masaladesi.club in the registration record from https://rdap.nic.club/domain/masaladesi.club.

Nameserver lila.ns.cloudflare.com is published for masaladesi.club in the registration record from https://rdap.nic.club/domain/masaladesi.club.

DNS

masaladesi.club has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.64.34, 172.67.175.154
AAAA2606:4700:3033::6815:4022, 2606:4700:3037::ac43:af9a
NSjobs.ns.cloudflare.com, lila.ns.cloudflare.com
MXroute1.mx.cloudflare.net (9), route3.mx.cloudflare.net (36), route2.mx.cloudflare.net (92)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at masaladesi.club is "v=spf1 include:spf.mailjet.com include:_spf.mx.cloudflare.net ~all".

IPv4 address 104.21.64.34 answers for masaladesi.club at resolver 1.1.1.1:53.

IPv4 address 172.67.175.154 answers for masaladesi.club at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3033::6815:4022 answers for masaladesi.club at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::ac43:af9a answers for masaladesi.club at resolver 1.1.1.1:53.

Mail exchanger route1.mx.cloudflare.net has preference 9.

Mail exchanger route3.mx.cloudflare.net has preference 36.

Mail exchanger route2.mx.cloudflare.net has preference 92.

Hosting and geo

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

Address104.21.64.34
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for masaladesi.club is valid, with 80 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectmasaladesi.club
Valid from21 October 2026
Valid until19 January 2027
Days left80
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.masaladesi.club, masaladesi.club.

Tech stack

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

  • Cloudflare · CDN
  • HTTP/3 · Miscellaneous

Cloudflare is filed under CDN.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 403 in 16 ms. The target title is 16 characters and the page has 0 H1 headings.

Status403
TTFB16 ms
Title length16 yes
Quoted title"Just a moment..."
Meta descriptionnone no
H1 count0
HSTSno no
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots metanoindex,nofollow
Canonical—
Languageen-US
Links0
Images0
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 masaladesi.club is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPyes

Cloudflare family DNS returned a block for masaladesi.club. That resolver covers adult and malware names.

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 10 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 5 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 0 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

  • October 2026: rdap created changed from empty to 2019-09-30T04:55:03Z.
  • October 2026: rdap dnssec changed from empty to no.
  • October 2026: rdap expires changed from empty to 2027-09-30T04:55:03Z.
  • October 2026: rdap nameservers changed from empty to jobs.ns.cloudflare.com,lila.ns.cloudflare.com.
  • October 2026: rdap registered changed from unknown to yes.
  • October 2026: rdap registrar changed from empty to GoDaddy.com, LLC.
  • October 2026: rdap statuses changed from empty to client delete prohibited,client renew prohibited,client transfer prohibited,client update prohibited.
  • October 2026: rdap updated changed from empty to 2026-09-28T03:01:22Z.

Questions

Is masaladesi.club safe?

Cloudflare family DNS returned a block for masaladesi.club. That resolver covers adult and malware names.

Who hosts masaladesi.club?

masaladesi.club is placed in Toronto, Canada.

When does masaladesi.club expire?

masaladesi.club expires on 30 September 2027 according to https://rdap.nic.club/domain/masaladesi.club.

Who owns masaladesi.club?

The registry did not return a person or a company for masaladesi.club. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

  • RDAP source https://rdap.nic.club/domain/masaladesi.club at 2026-10-30T13:37:08Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:37:08Z
  • TLS source tls:443 at 2026-10-30T13:37:08Z
  • HTTP source https://masaladesi.club/ at 2026-10-30T13:37:08Z
  • Tech source wappalyzergo at 2026-10-30T13:37:08Z
  • Geo source db-ip at 2026-10-30T13:37:08Z
  • Safety source family DNS and local lists at 2026-10-30T13:37:08Z

Methodology

Related reports

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

.club GoDaddy.com, LLC

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.