The available evidence contains more reassuring signals than material concerns. Its TLS certificate was valid at scan time. Registration records indicate a relatively young domain. The accessible homepage exposed no clear contact route and no obvious policy links. Confidence is high based on 7 distinct evidence groups collected during the latest scan. The result is a risk assessment, not proof that brixhub.to is legitimate or fraudulent.
Is brixhub.to safe?
Independent website safety report covering the connection, domain history, browser protections, page behavior and reputation signals observed by DarkOra.
What the latest scan says about brixhub.to
DarkOra separates technical evidence from community opinion and explains the factors behind the score.
Valid TLS certificate observed
Tonic
5 of 6 monitored headers
MDN HTTP Observatory result
Evidence that influenced the score
Review both columns. A high total score does not cancel a material caution signal.
Signals that support trust
Valid TLS certificate
The certificate is trusted, matches the hostname and is currently valid.
TLS · transport · +7 pointsHTTPS is active
The final page is delivered through an encrypted HTTPS connection.
Transport · transport · +4 pointsWebsite responded successfully
The scanned destination returned HTTP 200.
HTTP · transport · +3 pointsDomain email controls are published
The domain exposes multiple mail-routing or anti-spoofing controls.
DNS · domain · +2 pointsHSTS is present
The response includes the strict-transport-security header.
Security headers · security · +2 pointsNormal homepage content was accessible
The scanner received a usable HTML homepage rather than an interstitial or access-control page.
Content · behavior · +2 pointsNo monitored high-risk wording detected
The accessible homepage did not contain the monitored high-pressure or credential-request phrases.
Content · behavior · +2 pointsResponsive origin server
The initial request completed in about 191 ms.
Performance · transport · +1 pointsPublic DNS resolution
The domain resolves to 4 validated public network addresses.
DNS · domain · +1 pointsNameserver redundancy
At least two authoritative nameservers were found.
DNS · domain · +1 pointsPublic routing identity found
RIPEstat mapped the address to AS13335 and prefix 188.114.96.0/24.
RIPEstat · domain · +1 pointsMIME sniffing protection is present
The response includes the x-content-type-options header.
Security headers · security · +1 pointsReferrer policy is present
The response includes the referrer-policy header.
Security headers · security · +1 pointsPermissions policy is present
The response includes the permissions-policy header.
Security headers · security · +1 pointsClickjacking protection
Framing is restricted through X-Frame-Options or CSP.
Security headers · security · +1 pointsGood MDN Observatory grade
MDN HTTP Observatory assigned grade B.
MDN HTTP Observatory · security · +1 pointsDescriptive page title
The homepage provides a usable browser title.
Content · transparency · +1 pointsPage description is provided
The homepage includes a descriptive meta summary.
Content · transparency · +1 pointsrobots.txt is available
The website publishes a non-empty robots.txt file.
Public files · transparency · +1 pointsNo hidden frames or external form targets
The accessible homepage did not expose hidden iframes or forms posting to another hostname.
Content · behavior · +1 pointsSignals worth reviewing
Policy links not found
Privacy, terms, refund or company-information links were not detected.
Content · transparency · -2 pointsRelatively new domain
The domain appears to be about 98 days old. Newness alone does not prove fraud.
RDAP · domain · -1 pointsMissing content-security-policy
The response did not include this browser security header. Missing headers affect hardening, but do not by themselves prove fraud.
Security headers · security · -1 pointsContact route not found
No clear email, telephone or support route was detected on the homepage.
Content · transparency · -1 pointsVery limited page content
The homepage contains little readable text.
Content · transparency · -1 pointsNetwork, certificate and page-level observations
These values were captured at scan time and may change after a server, DNS or certificate update.
Infrastructure footprint
- Resolved IP addresses
- 188.114.96.0, 188.114.97.0, 2a06:98c1:3120::, 2a06:98c1:3121::
- Authoritative nameservers
- 2
- Mail / MX records
- 1
- CAA policy
- Not found
- SPF policy
- Published
- DMARC policy
- Published
Connection security
- HTTP status
- 200
- Final protocol
- HTTPS
- Certificate validation
- Trusted and valid
- Certificate issuer
- TLS protocol / cipher
- TLSv1.3 TLS_AES_256_GCM_SHA384
- Certificate expires
- November 17, 2026
Registration context
- Approximate age
- 98 days
- Registered
- June 26, 2026
- Expires
- June 26, 2028
- Registrar
- Tonic
- RDAP status entries
- 1
- RDAP available
- Yes
5/6 monitored protections detected
External security and reputation context
Provider failures stay separate from the base scan. DarkOra never fabricates a provider result.
DNSSEC authenticated data
The provider answered, but authenticated DNSSEC data was not confirmed.
Response code 0 · 2 answersIndependent header grade
MDN evaluated the live HTTP security configuration independently from DarkOra.
75 points · 11/12 tests passedPreload-list status
The hostname is not currently confirmed as preloaded. This alone is not a scam indicator.
Independent transport-hardening contextRouting and origin identity
The scanned address maps to prefix 188.114.96.0/24.
BGP present · registry presentOfficial threat-list context
The optional official Web Risk integration is not configured.
Checked Oct 2, 2026Official profile lookup
Trustpilot requires an official API key. DarkOra does not scrape profile pages.
Open Trustpilot profileResponse and redirect details
- Origin address used
- 188.114.96.0
- Server header
- cloudflare
- Content type
- text/html
- Downloaded response
- 1,065 bytes
- Redirect hops
- 0
- Initial response time
- 191 ms
What the homepage exposes
- Internal links
- 0
- External links
- 0
- External-link ratio
- 0%
- Forms detected
- 0
- Suspicious phrase groups
- 0
- Scanner methodology
- Version 4.0.0
Questions about this website safety report
Plain-language answers explain what the score can and cannot tell you.
Is brixhub.to safe to visit?+
The available evidence contains more reassuring signals than material concerns. Its TLS certificate was valid at scan time. Registration records indicate a relatively young domain. The accessible homepage exposed no clear contact route and no obvious policy links. Confidence is high based on 7 distinct evidence groups collected during the latest scan. The result is a risk assessment, not proof that brixhub.to is legitimate or fraudulent.
What is the DarkOra score for brixhub.to?+
The latest DarkOra website safety score is 74 out of 100, classified as Low observed risk. The score reflects observable technical and reputation evidence collected during the latest scan.
How is this website safety score calculated?+
DarkOra uses six independently capped areas: connection and TLS, domain maturity and DNS, browser security, identity and transparency, page behavior, and external reputation. No single signal determines the entire score.
When was brixhub.to last checked?+
The report was last updated on October 2, 2026. Website, DNS and certificate settings can change after this time.
Does a high score prove that brixhub.to is legitimate?+
No. Automated evidence can reduce uncertainty, but it cannot prove ownership, product quality or honest intent. Verify the organization, payment destination, refund terms and independent reputation before sharing sensitive information.
Reviews from DarkOra members
Account-linked reviews are screened for spam and published only after manual moderation.
No approved community review yet
Be the first member to describe a direct experience with this website.
Write a review
Sign in with your DarkOra account to submit a moderated review.
Sign in to reviewUse this report as one part of your decision. Automated checks can miss newly created threats and may flag legitimate configurations. Verify the organization, payment recipient, refund terms and independent reputation before sharing money, credentials or sensitive data.
