fullxcinema1.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 61 days left4 years old
25
fullxcinema1.com was registered on 1 Jul 2022 via NameCheap, Inc. and the registry expiry is 1 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fullxcinema1.com.
fullxcinema1.com publishes 2 nameservers. DNSSEC is not signed.
fullxcinema1.com has 1 IPv4 address (162.4.84.240). The geolocation database places 162.4.84.240 in Los Angeles, United States.
The TLS certificate from YE1 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
fullxcinema1.com was registered on 1 Jul 2022 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fullxcinema1.com.
| Registered | since 1 Jul 2022 |
|---|---|
| Created | 1 July 2022 |
| Updated | 2 August 2026 |
| Expires | 1 July 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.fp261.parklogic.com, ns2.fp261.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/fullxcinema1.com |
fullxcinema1.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.
Nameserver ns1.fp261.parklogic.com is published for fullxcinema1.com in the registration record from https://rdap.verisign.com/com/v1/domain/fullxcinema1.com.
Nameserver ns2.fp261.parklogic.com is published for fullxcinema1.com in the registration record from https://rdap.verisign.com/com/v1/domain/fullxcinema1.com.
DNS
fullxcinema1.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.240 |
|---|---|
| AAAA | — |
| NS | ns1.kefuhw.parklogic.com, ns2.kefuhw.parklogic.com |
| MX | mx156.hostedmxserver.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fullxcinema1.com is "v=spf1 -all".
IPv4 address 162.4.84.240 answers for fullxcinema1.com at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under fullxcinema1.com also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
fullxcinema1.com is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.240 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for fullxcinema1.com is not valid, with 61 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | fullxcinema1.com |
| Valid from | 2 October 2026 |
| Valid until | 31 December 2026 |
| Days left | 61 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fullxcinema1.com.
Validation result: certificate did not validate
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 |
|---|
Get "https://fullxcinema1.com/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for fullxcinema1.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for fullxcinema1.com. 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 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 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 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: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is fullxcinema1.com safe?
Cloudflare family DNS returned a block for fullxcinema1.com. That resolver covers adult and malware names.
Who hosts fullxcinema1.com?
fullxcinema1.com is placed in Los Angeles, United States.
When does fullxcinema1.com expire?
fullxcinema1.com expires on 1 July 2027 according to https://rdap.verisign.com/com/v1/domain/fullxcinema1.com.
Who owns fullxcinema1.com?
The registry did not return a person or a company for fullxcinema1.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/fullxcinema1.com at 2026-10-30T13:55:29Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:55:29Z
- TLS source tls:443 at 2026-10-30T13:55:29Z
- HTTP source https://fullxcinema1.com/ at 2026-10-30T13:55:29Z
- Tech source not available at 2026-10-30T13:55:29Z
- Geo source db-ip at 2026-10-30T13:55:29Z
- Safety source family DNS and local lists at 2026-10-30T13:55:29Z
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.