Website trust check
Is tiktokmysterybox.shop safe to use?
Below is an automated, evidence-based snapshot of tiktokmysterybox.shop showing risk indicators, trust signals, and technical checks. Results are not legal or financial advice and are not a guarantee that a site is safe or unsafe.
Snapshot only. Data comes from public feeds, technical checks, and limited page context. Phishing and scam sites change quickly—use your judgment and official channels when in doubt.
- Trust-style score
- 58 / 100
- Domain age (days)
- —
- SSL / HTTPS
- No HTTPS
Caution
Trust score (automated)
Analyzed domain
tiktokmysterybox.shop
Key risk indicators
Warnings and higher-severity context from this run.
HTTPS/TLS connection not established
A TLS handshake to port 443 did not complete successfully in this probe.
Source: TLS certificate checkConfidence: high
Trust signals
Supportive or informational context (including “no hit” messages).
RDAP lookup failed
HTTP 429
Source: RDAP (rdap.org)Confidence: lowGoogle Safe Browsing not configured
No API key is set, so threat matches cannot be requested.
Source: Google Safe BrowsingConfidence: highURLhaus unavailable
HTTP 401
Source: URLhausConfidence: lowNo domain string match in cached Police pages
No direct domain string overlap was detected in lightly cached excerpts of the referenced politie.nl pages.
Source: Dutch Police (public pages)Confidence: lowNo OpenPhish feed match
No overlapping entry was found in the fetched OpenPhish feed for this check window.
Source: OpenPhishConfidence: medium
Domain information
- Registration date: unknown
- Domain age (days): unknown
- Registrar: unknown
- Country: unknown
- Expiration date: unknown
- Privacy / redacted ownership hints: no / unknown
Source: RDAP (rdap.org)
Security checks
- HTTPS/TLS reachable: no
- Certificate trusted in probe: no
- Possibly self-signed / untrusted: no / unknown
- Issuer: unknown
- Expiry: unknown
Source: TLS certificate check
Intelligence sources
Normalized provider output. “Matched” means the provider reported a hit or pattern in this run.
- HTTPS/TLS connection not establishedsslmatched
A TLS handshake to port 443 did not complete successfully in this probe.
Source: TLS certificate check · severity: danger · confidence: high
- RDAP lookup faileddomainno match
HTTP 429
Source: RDAP (rdap.org) · severity: info · confidence: low
- Google Safe Browsing not configuredmalwareno match
No API key is set, so threat matches cannot be requested.
Source: Google Safe Browsing · severity: info · confidence: high
- URLhaus unavailablemalwareno match
HTTP 401
Source: URLhaus · severity: info · confidence: low
- No domain string match in cached Police pagesgovernmentno match
No direct domain string overlap was detected in lightly cached excerpts of the referenced politie.nl pages.
Source: Dutch Police (public pages) · severity: positive · confidence: low
- No OpenPhish feed matchphishingno match
No overlapping entry was found in the fetched OpenPhish feed for this check window.
Source: OpenPhish · severity: positive · confidence: medium
Review signals
No public review data found yet.
- No public review signals found
No public reviews or Google listings were found, indicating a lack of trust signals.
Sources: Google Places API (searchText)
- No Google Places result matched this domain's website.
Reputation Signals
No external reputation profile found. This does not automatically mean unsafe.
Supply chain
Dropshipping: unlikely · China-linked fulfillment: unlikely · Local stock/production: unlikely · Confidence: low · Score nudge: 0
- Not enough website text to assess supply chain.
Score evidence (debug)
Signed contributions toward the server risk score (positive numbers increase risk, negative numbers reduce it).
- No reliable HTTPS endpoint (+22) — Port 443 probe did not complete a TLS session. · TLS certificate check
AI summary & key factors
Blended automated notes (heuristics, intel-weighted scoring context, and optional AI). This is not legal or financial advice.
- AI risk signal: high
- The domain name is unusually long, which is common in phishing patterns.
- A TLS handshake to port 443 did not complete successfully, indicating a lack of a reliable HTTPS connection.
AI model used in this run: yes