What is this website?
22bet.com is currently classified in the Sports Betting category based on observed public pages. The sampled pages were marked as English-language.
No listed local patterns observedHomepage-only analysis is not a malware clearance. Read the scope and findings below.
How to read this report
Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.
No automated scan can guarantee that a website is safe.
Independent evidence brief
What we observed about 22bet.com
The latest scan examined 0 public pages on 22bet.com. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.
Purpose and visible content
On its homepage, the site says: 22Bet Betting Company. Licensed sports betting. Online bets 24/7.
Observed page title: 22BET - Online Sports Betting and Best Odds.
Registrar and domain history
Registered on Jul 21, 2012. Registrar: GoDaddy.com, LLC.
Recorded expiry date: Jul 21, 2028. Registry data can change.
Connection and hosting evidence
The checked homepage returned HTTP 200 in about 14000 ms.
A valid TLS certificate was observed, expiring Apr 3, 2027.
Threat checks and score context
External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.
Safety Score: 72/100. Evidence Confidence: 70%. These measure different things.
Latest recorded material change: Safety score updated from 74 to 73.
At a glance
Key findings
Report is current
The displayed evidence comes from the published immutable scan.
Confidence is separate
Unavailable evidence is shown as missing and never counted as clean.
Verify before sensitive actions
Check the exact URL and context before payments, credentials, or downloads.
Fully explainable
Why this score?
Threat providers were unavailable. The neutral uncertainty baseline is not a clean verdict.
Domain registration age and expiry were checked.
Observed DNS records and network address were checked.
Observed certificate validity and TLS protocol were checked.
Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.
Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.
Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.
Observed HTTP status and final connection scheme were checked.
Server-side analysis
Automated security checks
Homepage HTML only · Eight local rule families · local-security-v1
Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.
No listed local patterns observed. The limited rule set cannot detect every threat or behavior.
External threat intelligence
Local checks do not query external reputation databases. An unavailable check is never a clean result.
Registration
Domain information
Infrastructure
Network & hosting
At a glance
Infrastructure summary
A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.
Page telemetry
Observed page statistics
These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.
Encrypted transport
TLS certificate
Resolution
DNS footprint
DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.
94.241.132.4TTL —dns41.cloudns.netTTL —dns42.cloudns.netTTL —dns43.cloudns.netTTL —dns44.cloudns.netTTL —1 aspmx.l.google.comTTL —10 alt3.aspmx.l.google.comTTL —10 alt4.aspmx.l.google.comTTL —5 alt1.aspmx.l.google.comTTL —5 alt2.aspmx.l.google.comTTL —atlassian-domain-verification=UpfGjMs5ikCrCmZWYJ/0AQfaUSnZC7c5NWIPuLoWhkTaJLz9If4u5hAjsV2OobNNTTL —google-site-verification=Fstnf-O7Lc-tRFf3t-uqH4JRd64ws3deBCxQhNblRdMTTL —google-site-verification=IuxGuVAWt1BTIrMDu7Dw_353I2NWB-5bZDP2e5EAuiMTTL —v=spf1 include:customeriomail.com include:_spf.google.com ip4:5.45.86.247 ip4:77.72.17.2 ip4:77.72.17.18 ip4:93.189.56.10 ip4:188.143.232.142 ~allTTL —Responsible disclosure
security.txt
No readable security.txt file was observed at the standard locations. This is informational and is not evidence of malware.
Browser protections
Security headers
Response headers
Cookie protections
No Set-Cookie header was observed on the sampled homepage response. Other pages may set cookies separately.
Detected stack
Technologies
Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.
JavaScript library advisories
JavaScript advisory analysis was not recorded for this scan.
Structured facts
Website identity & response
Connection path
Redirect chain
The chain is shown exactly as observed by the scanner. A redirect is not itself a malware finding, but unexpected domains or an HTTP downgrade deserve review.
Compared with the previous scan
What changed
This comparison uses persisted scan evidence only. A changed signal can reflect a real website change, a different response or newly available evidence.
Explainable matching
Digital fingerprint
Comparable components help find technically related websites. A match does not prove common ownership.
Material changes only
Change history
score changed
screenshot changed
screenshot changed
Visual evidence
Website screenshot
For site owners
Show your verified trust report
Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.
Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.
Questions about 22bet.com
FAQ
Is 22bet.com safe to visit?
The latest Safety Score is 72/100 with 70% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.
Did the scan detect malware on 22bet.com?
External threat-provider coverage was unavailable for this scan, so malware status is unverified.
When was 22bet.com registered?
The public registry record shows Jul 21, 2012. Registration details may be privacy-protected or updated later.
Did 22bet.com have a valid TLS certificate?
The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.
Can a paid listing change this website's score?
No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.