factsreader.com
factsreader.com blocks automated analysis, answering with HTTP 500 server error instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis. It answered our request with HTTP 500 server error rather than its homepage, so nothing below is derived from its actual content — doing so would describe the bot wall, not the site. The certificate and robots.txt data are still accurate, because those are served to everyone.
How does factsreader.com compare with other domains analysed here?
Measured against the 79 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 23% of them (median 657ms) |
|---|---|
| Domain age | Older than 76% of them |
Related domains in this index
Other analysed domains served from the same country:
When was factsreader.com registered?
factsreader.com was registered on 8 March 2022, which makes it about 4 years old.
The registrar of record is HOSTINGER operations, UAB.
Registration runs until 8 March 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 8 March 2022 |
|---|---|
| Expires | 8 March 2027 |
| Registrar | HOSTINGER operations, UAB |
| Registry status | client transfer prohibited |
Where is factsreader.com hosted?
The first address resolves to infrastructure in Singapore, Singapore.
The network is operated by Choopa (AS20473 The Constant Company, LLC).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is factsreader.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of factsreader.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 500 over HTTPS.
At 1302ms to first byte this response is slow for a homepage measured from a single European location.
At 3KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | BitNinja-Waf3, LiteSpeed |
|---|---|
| Compression | gzip |
| Page size | 2,711 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is factsreader.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is valid until 2026-12-19, which is 75 days from the date of this check. It covers 2 hostnames.
- *.factsreader.com
- factsreader.com
The certificate has 75 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for factsreader.com?
| IP addresses | 139.180.187.142 |
|---|---|
| Reverse DNS | indigo.herosite.pro |
| Name servers | us.solidhosting.pro, in.solidhosting.pro, sg.solidhosting.pro, eu.solidhosting.pro |
| Mail (MX) | factsreader.com (pri 0) |
| SPF | v=spf1 +a +mx +ip4:139.180.187.142 include:relay.mailbaby.net ~all |
| TXT records | 1 |
factsreader.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to indigo.herosite.pro, which usually names the hosting provider.
Can factsreader.com be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 103 bytes and names 1 user-agent group. It does not blanket-disallow general crawlers.
Sitemaps declared:
- http://factsreader.com/sitemap_index.xml
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does factsreader.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own factsreader.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →