fanprojplay.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 83 days leftUnder 1 year old
52
fanprojplay.net was registered on 2 Mar 2026 via NameCheap, Inc. and the registry expiry is 2 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/fanprojplay.net.
fanprojplay.net publishes 2 nameservers. DNSSEC is not signed.
fanprojplay.net has 2 IPv4 addresses (104.21.27.112, 172.67.169.35) and 2 IPv6 addresses (2606:4700:3032::6815:1b70, 2606:4700:3034::ac43:a923). The geolocation database places 104.21.27.112 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 83 days left (TLS 1.3).
No safety warning was recorded for fanprojplay.net in the checks that ran.
Domain · RDAP/WHOIS
fanprojplay.net was registered on 2 Mar 2026 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/fanprojplay.net.
| Registered | since 2 Mar 2026 |
|---|---|
| Created | 2 March 2026 |
| Updated | 2 March 2026 |
| Expires | 2 March 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | alexandra.ns.cloudflare.com, bradley.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/fanprojplay.net |
fanprojplay.net 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.
Nameserver alexandra.ns.cloudflare.com is published for fanprojplay.net in the registration record from https://rdap.verisign.com/net/v1/domain/fanprojplay.net.
Nameserver bradley.ns.cloudflare.com is published for fanprojplay.net in the registration record from https://rdap.verisign.com/net/v1/domain/fanprojplay.net.
DNS
fanprojplay.net has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.27.112, 172.67.169.35 |
|---|---|
| AAAA | 2606:4700:3032::6815:1b70, 2606:4700:3034::ac43:a923 |
| NS | alexandra.ns.cloudflare.com, bradley.ns.cloudflare.com |
| MX | eforward1.registrar-servers.com (10), eforward2.registrar-servers.com (10), eforward3.registrar-servers.com (10), eforward4.registrar-servers.com (15), eforward5.registrar-servers.com (20) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fanprojplay.net is "v=spf1 include:spf.efwd.registrar-servers.com ~all".
IPv4 address 104.21.27.112 answers for fanprojplay.net at resolver 1.1.1.1:53.
IPv4 address 172.67.169.35 answers for fanprojplay.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:1b70 answers for fanprojplay.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:a923 answers for fanprojplay.net at resolver 1.1.1.1:53.
Mail exchanger eforward1.registrar-servers.com has preference 10.
Mail exchanger eforward2.registrar-servers.com has preference 10.
Mail exchanger eforward3.registrar-servers.com has preference 10.
Mail exchanger eforward4.registrar-servers.com has preference 15.
Mail exchanger eforward5.registrar-servers.com has preference 20.
Hosting and geo
fanprojplay.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.27.112 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for fanprojplay.net is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | fanprojplay.net |
| Valid from | 25 October 2026 |
| Valid until | 23 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.fanprojplay.net, fanprojplay.net.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for fanprojplay.net is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
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 0 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 2 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 fanprojplay.net 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 fanprojplay.net?
fanprojplay.net is placed in Toronto, Canada.
When does fanprojplay.net expire?
fanprojplay.net expires on 2 March 2027 according to https://rdap.verisign.com/net/v1/domain/fanprojplay.net.
Who owns fanprojplay.net?
The registry did not return a person or a company for fanprojplay.net. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/fanprojplay.net at 2026-10-30T14:51:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:51:59Z
- TLS source tls:443 at 2026-10-30T14:51:59Z
- HTTP source https://fanprojplay.net/ at 2026-10-30T14:51:59Z
- Tech source not available at 2026-10-30T14:51:59Z
- Geo source db-ip at 2026-10-30T14:51:59Z
- Safety source family DNS and local lists at 2026-10-30T14:51:59Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.