xfltd.cc

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

OfflineSafe3 years old

One re-check per domain each UTC day.

35

xfltd.cc was registered on 24 Feb 2023 via Dynadot Inc and the registry expiry is 24 Feb 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc.

xfltd.cc publishes 2 nameservers. DNSSEC is not signed.

xfltd.cc has 1 IPv4 address (47.104.131.17). The geolocation database places 47.104.131.17 in Qingdao, China.

No safety warning was recorded for xfltd.cc in the checks that ran.

Domain · RDAP/WHOIS

xfltd.cc was registered on 24 Feb 2023 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc.

Registeredsince 24 Feb 2023
Created24 February 2023
Updated7 January 2026
Expires24 February 2027
RegistrarDynadot Inc
Statusclient transfer prohibited
Nameserversjaziel.ns.cloudflare.com, sima.ns.cloudflare.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc

xfltd.cc 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 jaziel.ns.cloudflare.com is published for xfltd.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc.

Nameserver sima.ns.cloudflare.com is published for xfltd.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc.

DNS

xfltd.cc has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A47.104.131.17
AAAA—
NSjaziel.ns.cloudflare.com, sima.ns.cloudflare.com
MXroute2.mx.cloudflare.net (43), route3.mx.cloudflare.net (60), route1.mx.cloudflare.net (87)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at xfltd.cc is "v=spf1 include:_spf.mx.cloudflare.net ~all".

IPv4 address 47.104.131.17 answers for xfltd.cc at resolver 1.1.1.1:53.

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

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

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

Hosting and geo

xfltd.cc is placed in Qingdao, China by the local geolocation database (db-ip).

Address47.104.131.17
CountryChina
CityQingdao
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

No TLS certificate was read for xfltd.cc on port 443.

Availableno
Sourcetls:443

dial tcp: lookup xfltd.cc: i/o timeout

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

Get "https://www.xfltd.org/": context deadline exceeded

Security

Family DNS for xfltd.cc is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
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 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 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 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: dns a changed from 118.190.150.73 to 47.104.131.17.
  • October 2026: tls issuer changed from Amazon RSA 2048 M01 to empty.
  • October 2026: tls not_after changed from 2027-03-13T23:59:59Z to empty.
  • October 2026: tls protocol changed from TLS 1.3 to empty.
  • October 2026: tls valid changed from true to false.
  • October 2026: geo city changed from empty to Qingdao.
  • October 2026: geo country changed from empty to China.

Questions

Is xfltd.cc 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 xfltd.cc?

xfltd.cc is placed in Qingdao, China.

When does xfltd.cc expire?

xfltd.cc expires on 24 February 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc.

Who owns xfltd.cc?

The registry did not return a person or a company for xfltd.cc. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.

Sources

  • RDAP source https://tld-rdap.verisign.com/cc/v1/domain/xfltd.cc at 2026-10-30T13:36:14Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:36:14Z
  • TLS source tls:443 at 2026-10-30T13:36:14Z
  • HTTP source https://xfltd.cc/ at 2026-10-30T13:36:14Z
  • Tech source not available at 2026-10-30T13:36:14Z
  • Geo source db-ip at 2026-10-30T13:36:14Z
  • Safety source family DNS and local lists at 2026-10-30T13:36:14Z

Methodology

Related reports

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

.cc Dynadot 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.