flixhq.pro

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

Online · 200SafeSSL: 41 days leftUnder 1 year old

One re-check per domain each UTC day.

67

flixhq.pro was registered on 27 Feb 2026 via Sav.com, LLC and the registry expiry is 27 Feb 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/flixhq.pro.

flixhq.pro publishes 2 nameservers. DNSSEC is not signed.

flixhq.pro has 2 IPv4 addresses (157.90.33.73, 157.90.33.74). The geolocation database places 157.90.33.73 in Falkenstein, Germany.

The TLS certificate from YR2 is valid and has 41 days left (TLS 1.2). The homepage answered HTTP 200.

Tech detection named Angie, C and Perl. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for flixhq.pro in the checks that ran.

Domain · RDAP/WHOIS

flixhq.pro was registered on 27 Feb 2026 via Sav.com, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/flixhq.pro.

Registeredsince 27 Feb 2026
Created27 February 2026
Updated12 August 2026
Expires27 February 2027
RegistrarSav.com, LLC
Statusclient transfer prohibited
Nameserversns1.park-my-domain.net, ns2.park-my-domain.net
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/flixhq.pro

flixhq.pro 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.park-my-domain.net is published for flixhq.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/flixhq.pro.

Nameserver ns2.park-my-domain.net is published for flixhq.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/flixhq.pro.

DNS

flixhq.pro has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A157.90.33.73, 157.90.33.74
AAAA—
NSns1.park-my-domain.net, ns2.park-my-domain.net
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 157.90.33.73 answers for flixhq.pro at resolver 1.1.1.1:53.

IPv4 address 157.90.33.74 answers for flixhq.pro at resolver 1.1.1.1:53.

A random label under flixhq.pro also resolved, which means wildcard DNS is on.

Hosting and geo

flixhq.pro is placed in Falkenstein, Germany by the local geolocation database (db-ip).

Address157.90.33.73
CountryGermany
CityFalkenstein
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for flixhq.pro is valid, with 41 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subjectflixhq.pro
Valid from12 September 2026
Valid until11 December 2026
Days left41
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: *.flixhq.pro, flixhq.pro.

Tech stack

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

  • Angie · Web servers
  • C · Programming languages
  • Perl · Programming languages

Angie is filed under Web servers.

C is filed under Programming languages.

Perl is filed under Programming languages.

On-page checks

The homepage returned HTTP 200 in 3 ms. The target title is 0 characters and the page has 2 H1 headings.

Status200
TTFB3 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count2
HSTSno no
CSPyes
X-Frame-Options—
Robots metanoindex,noarchive,nofollow
Canonical—
Languageen
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 flixhq.pro 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
CSPyes

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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 5 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

  • October 2026: geo city changed from empty to Falkenstein.
  • October 2026: geo country changed from empty to Germany.

Questions

Is flixhq.pro 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 flixhq.pro?

flixhq.pro is placed in Falkenstein, Germany.

When does flixhq.pro expire?

flixhq.pro expires on 27 February 2027 according to https://rdap.identitydigital.services/rdap/domain/flixhq.pro.

Who owns flixhq.pro?

The registry did not return a person or a company for flixhq.pro. RDAP often redacts the registrant. The registrar on file is Sav.com, LLC.

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/flixhq.pro at 2026-10-30T15:56:29Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:56:29Z
  • TLS source tls:443 at 2026-10-30T15:56:29Z
  • HTTP source https://flixhq.pro/ at 2026-10-30T15:56:29Z
  • Tech source wappalyzergo at 2026-10-30T15:56:29Z
  • Geo source db-ip at 2026-10-30T15:56:29Z
  • Safety source family DNS and local lists at 2026-10-30T15:56:29Z

Methodology

Related reports

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

.pro Sav.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.