pixhost.to

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

Online · 200SafeSSL: 32 days left8 years oldTranco #7255

One re-check per domain each UTC day.

65

pixhost.to was registered on 28 Mar 2018 via Tonic and the registry expiry is 28 Mar 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/pixhost.to.

pixhost.to publishes 2 nameservers. DNSSEC is not signed.

pixhost.to has 1 IPv4 address (94.229.45.2). The geolocation database places 94.229.45.2 in Petržalka, Slovakia.

The TLS certificate from YE2 is valid and has 32 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Clipboard.js, HTTP/3, Nginx, Plupload, jQuery and jQuery UI. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for pixhost.to in the checks that ran.

Domain · RDAP/WHOIS

pixhost.to was registered on 28 Mar 2018 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/pixhost.to.

Registeredsince 28 Mar 2018
Created28 March 2018
Updated11 August 2026
Expires28 March 2027
RegistrarTonic
Statusactive
Nameserverskiki.bunny.net, coco.bunny.net
DNSSECno
Sourcehttps://rdap.tonicregistry.to/rdap/domain/pixhost.to

Nameserver kiki.bunny.net is published for pixhost.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/pixhost.to.

Nameserver coco.bunny.net is published for pixhost.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/pixhost.to.

DNS

pixhost.to has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A94.229.45.2
AAAA—
NScoco.bunny.net, kiki.bunny.net
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 94.229.45.2 answers for pixhost.to at resolver 1.1.1.1:53.

A random label under pixhost.to also resolved, which means wildcard DNS is on.

Hosting and geo

pixhost.to is placed in Petržalka, Slovakia by the local geolocation database (db-ip).

Address94.229.45.2
CountrySlovakia
CityPetržalka
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for pixhost.to is valid, with 32 days left and 2 subject alternative names. Source: tls:443.

IssuerYE2
Subjectpixhost.to
Valid from4 September 2026
Valid until3 December 2026
Days left32
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.pixhost.to, pixhost.to.

Tech stack

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

  • Clipboard.js · JavaScript libraries
  • HTTP/3 · Miscellaneous
  • Nginx · Web servers, Reverse proxies
  • Plupload · JavaScript libraries
  • jQuery · JavaScript libraries
  • jQuery UI · JavaScript libraries

Clipboard.js is filed under JavaScript libraries.

HTTP/3 is filed under Miscellaneous.

Nginx is filed under Web servers, Reverse proxies.

Plupload is filed under JavaScript libraries.

jQuery is filed under JavaScript libraries.

jQuery UI is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 20 ms. The target title is 35 characters and the page has 1 H1 heading.

Status200
TTFB20 ms
Title length35 yes
Quoted title"Pixhost – Kostenloses Bilderhosting"
Meta description"Pixhost – kostenloses Bilderhosting. Laden Sie Ihre Bilder kostenlos hoch, bis zu 10 MB pro Bild!" yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots metaindex,follow
Canonical—
Languagede
Links13
Images0
Faviconyes

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 pixhost.to 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 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 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: geo city changed from empty to Petržalka.
  • October 2026: geo country changed from empty to Slovakia.

Questions

Is pixhost.to 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 pixhost.to?

pixhost.to is placed in Petržalka, Slovakia.

When does pixhost.to expire?

pixhost.to expires on 28 March 2027 according to https://rdap.tonicregistry.to/rdap/domain/pixhost.to.

Who owns pixhost.to?

The registry did not return a person or a company for pixhost.to. RDAP often redacts the registrant. The registrar on file is Tonic.

Sources

  • RDAP source https://rdap.tonicregistry.to/rdap/domain/pixhost.to at 2026-10-30T15:16:50Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:16:50Z
  • TLS source tls:443 at 2026-10-30T15:16:50Z
  • HTTP source https://pixhost.to/ at 2026-10-30T15:16:50Z
  • Tech source wappalyzergo at 2026-10-30T15:16:50Z
  • Geo source db-ip at 2026-10-30T15:16:50Z
  • Safety source family DNS and local lists at 2026-10-30T15:16:50Z

Methodology

Related reports

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

.to Tonic

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.