scan.page

#6A828589 · Safe
70 / 100
AssureBlade · scan.page — Report card
172.66.42.239 Valid HTTPS 0.9 years Namecheap Inc. Updated

Reading the signals of scan.page

The numbers below come straight from scan.page's live DNS, TLS and RDAP responses. We do not store editorial opinions.

Technical Information

IP Address
172.66.42.239
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
WE1
Valid Until
2026-06-27

Registrar

Registrar
Namecheap Inc.
Registered On
2025-06-05
Expires On
2026-06-05
Domain Age
0.9 years

Technical Overview

The domain scan.page is reachable and resolves to Unknown via Unknown. Below we walk through the most relevant signals one by one.

Browser compatibility

Mainstream browsers will accept scan.page's TLS configuration if our probe returns "OK". The current value is: OK.

Maturity check

Maturity-wise, scan.page falls in the "new" bracket — about 0.9 years on record. Most short-lived scams operate on domains under 12 months old, so age helps but does not exclude risk.

Routing & ISP

Traffic to scan.page currently terminates at Unknown in Unknown — visible to anyone running a traceroute. Hosting-country mismatches with the brand audience can be a useful signal.

Beyond the technical score

A clean technical profile only proves scan.page follows industry plumbing standards. It does NOT prove honest content. Always read the actual site before transacting.

Bottom line

scan.page ends up at 70/100 — that is safe in our scale. The result is computed from public technical data only, no human review.

Frequently Asked Questions

What is the registration date of scan.page?
RDAP reports scan.page at about 0.9 years of age — placed in the "new" maturity bracket.
Where was scan.page bought?
The domain is registered through Namecheap Inc..
What goes into the scan.page trust rating?
The score is computed from technical signals only — it is not a human review and should not be your sole decision input.
Is the WHOIS information about scan.page hidden?
Most modern registrars apply privacy protection by default, so personal contact data may be redacted. Registration dates and registrar are still visible.
Is scan.page on a security blocklist?
At the time of audit, scan.page was not present in the public blocklists we sample (PhishTank, abuse feeds, etc.).

What looks good

  • Registrar verified by ICANN
  • Certificate validity window is current
  • Reachable on standard ports
  • Certificate issued by a recognised CA

What to watch

  • Privacy-protected WHOIS — operator not directly visible
  • Registrar based outside the target audience country
  • No corporate footprint linked to the domain

This report is generated automatically from public technical signals. It is not legal or financial advice.

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →