Skip to security report
chahinekallouch30-bot.github.io favicon
Domain security and threat intelligence

chahinekallouch30-bot.github.io

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The domain chahinekallouch30-bot.github.io hosted a fraudulent Roblox login page designed to capture account usernames and passwords. If you entered your credentials here, immediately change your password on the official roblox.com site and check your account sessions.

More about the sources
Recorded security signals

Stored VirusTotal result: 7/92 engines flagged. Malicious: 6. Suspicious: 1. Analysis time (as stored): 2026-11-22 00:07 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish. Use caution — do not enter credentials or personal information.

VirusTotal detections: 7/92 Stored blocklist matches: 1
Registrar
GitHub
Resolved IP
185.199.108.153
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded chahinekallouch30-bot.github.io on 2026-11-22. Stored VirusTotal result: 7/92 engines flagged. Malicious: 6. Suspicious: 1. Analysis time (as stored): 2026-11-22 00:07 UTC. Retrieved (as stored): 2026-11-22 15:34 UTC. Listed by external blocklists: OpenPhish. Risk: critical (evidence score 75/100). Registrar: GitHub. Do not enter credentials or connect a wallet.

Critical
VirusTotal
7 / 92
Blocklist matches
1 external + PhishDestroy list
Hosting
185.199.108.153
Registrar
GitHub
Page captures
2

Stored capture capture · 2026-11-22 15:27 UTC · SHA-256 04e6d8ec…6c616e7

PhishDestroy analysis, reviewed version

Roblox login page layout and credential harvesting form

The page presents a dark-themed login interface mimicking Roblox, titled "Connexion Roblox" with the subtitle "Connecte-toi pour continuer". It displays two input fields labeled respectively "Nom d'utilisateur ou Email" and "Mot de passe" to capture user credentials. Below the input fields, a bright blue button reads "Se connecter" to submit the form data to the attackers. A small copyright notice at the bottom reads "© 2026 Roblox Corporation" to deceive visitors into believing it is an authentic portal. Instead of connecting to roblox.com, the form harvests the entered account credentials directly for unauthorized access.

Security telemetry and threat assessment

urlscan classified the page as malicious, 7 of 92 engines on VirusTotal flagged it on 22 Nov 2026, and OpenPhish blocks it, with Fortinet, Sophos and Netcraft among the flagging vendors. Its PhishDestroy evidence score is 75/100 (critical). Because the domain runs on github.io and uses a deceptive path resembling the target brand, it functions entirely to intercept user logins away from the official roblox.com platform.

Recommended actions for affected users

Visitors who entered their username and password into this form should immediately secure their accounts by changing their credentials on the official roblox.com website. Enable two-factor authentication and terminate any active sessions tied to unknown devices. Report the URL to hosting abuse to prevent further credential collection.

Source evidenceVirusTotal 7 / 92 4 sources

VirusTotal

7 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
7
Denominator
92
Vendors
Emsisoft, Fortinet, G-Data, Netcraft, SOCRadar, Sophos, Webroot
Observed at
2026-11-22 00:07:48
Checked at
2026-11-22 16:34:26
Fetched at
2026-11-22 15:34:27
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
chahinekallouch30-bot.github.io — Fraudulent Roblox sign-in
AI description
chahinekallouch30-bot.github.io hosted a fake Roblox sign-in page capturing passwords, flagged by urlscan and 7 VirusTotal engines. Do not submit credentials.
AI summary
Roblox login page layout and credential harvesting form The page presents a dark-themed login interface mimicking Roblox, titled "Connexion Roblox" with the subtitle "Connecte-toi pour continuer". It displays two input fields labeled respectively "Nom d'utilisateur ou Email" and "Mot de passe" to capture user credentials. Below the input fields, a bright blue button reads "Se connecter" to submit the form data to the attackers. A small copyright notice at the bottom reads "© 2026 Roblox Corporation" to deceive visitors into believing it is an authentic portal. Instead of connecting to roblox.com, the form harvests the entered account credentials directly for unauthorized access. Security telemetry and threat assessment urlscan classified the page as malicious, 7 of 92 engines on VirusTotal flagged it on 22 Nov 2026, and OpenPhish blocks it, with Fortinet, Sophos and Netcraft among the flagging vendors. Its PhishDestroy evidence score is 75/100 (critical). Because the domain runs on github.io and uses a deceptive path resembling the target brand, it functions entirely to intercept user logins away from the official roblox.com platform. Recommended actions for affected users Visitors who entered their username and password into this form should immediately secure their accounts by changing their credentials on the official roblox.com website. Enable two-factor authentication and terminate any active sessions tied to unknown devices. Report the URL to hosting abuse to prevent further credential collection.
AI generated by
threat-v10-gemini
AI generated at
2026-11-22T15:38:58Z
Revision
06e026515f44d829fa38b1694d54544064ff60dec36573e70c86bc722dd3dce1
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
chahinekallouch30-bot.github.io
Allowed issuers
  • sectigo.com
  • digicert.com
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
DNS zone
github.io

Page quality

Layout shift (CLS)
0
SEO score
82
Speed Index, s
0.79
First Contentful Paint (FCP), s
0.79
Largest Contentful Paint (LCP), s
0.79
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
55
Best practices score
92

Location

IP address
2606:50c0:8000::153
ASN
54113
Organization
Fastly, Inc.
Country
US

TLS certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Key size, bits
2048
Certificate chain
  • *.github.io
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
06A65E5D3279BA564A4DE74EB5D64478DBB8
SHA-256
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Subject
*.github.io
Valid until
Valid from

DNS records

A
  • 185.199.111.153
  • 185.199.109.153
  • 185.199.110.153
  • 185.199.108.153
AAAA
  • 2606:50c0:8002::153
  • 2606:50c0:8001::153
  • 2606:50c0:8003::153
  • 2606:50c0:8000::153

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8003::153
IP version
6

Technology stack

Technologies
  • Varnish
  • GitHub Pages
  • Fastly

HTTP headers

Response headers
Server
GitHub.com
Content-Type
text/html; charset=utf-8
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Via
1.1 varnish
X-Cache
HIT
X-Cache-Hits
1
X-Served-By
cache-fra-etou8220140-FRA
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 6; Domain: chahinekallouch30-bot.github.io; Issuers: sectigo.com, digicert.com, letsencrypt.org
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 198.51.44.5; Host: dns1.p05.nsone.net), (IP: 198.51.45.5; Host: dns2.p05.nsone.net), (IP: 198.51.44.69; Host: dns3.p05.nsone.net), (IP: 198.51.45.69; Host: dns4.p05.nsone.net), (IP: 205.251.197.59; Host: ns-1339.awsdns-39.org), (IP: 205.251.198.86; Host: ns-1622.awsdns-10.co.uk), (IP: 205.251.193.137; Host: ns-393.awsdns-49.com), (IP: 205.251.194.180; Host: ns-692.awsdns-22.net); Zone: github.io
Quality
Cls: 0; Seo: 82; Si s: 0.79; Fcp s: 0.79; Lcp s: 0.79; Tbt ms: 0; Performance: 100; Accessibility: 55; Best practices: 92
Location
IP: 2606:50c0:8000::153; ASN: 54113; Org: Fastly, Inc.; Country: US
SSL
San: *.github.com, *.github.io, *.githubusercontent.com, github.com, github.io, githubusercontent.com; Bits: 2048; Chain: *.github.io, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 06A65E5D3279BA564A4DE74EB5D64478DBB8; SHA256: f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856; Subject: *.github.io; Valid to: 2026-12-29T23:44:45Z; Valid from: 2026-09-30T23:44:46Z
DNS records
A: 185.199.111.153, 185.199.109.153, 185.199.110.153, 185.199.108.153; Aaaa: 2606:50c0:8002::153, 2606:50c0:8001::153, 2606:50c0:8003::153, 2606:50c0:8000::153
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2606:50c0:8003::153; Family: 6
Tech stack
Technologies: Varnish, GitHub Pages, Fastly
HTTP headers
Headers: Server: GitHub.com; Content type: text/html; charset=utf-8; Content security policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Via: 1.1 varnish; X cache: HIT; X cache hits: 1; X served by: cache-fra-etou8220140-FRA

Questions about chahinekallouch30-bot.github.io

Is chahinekallouch30-bot.github.io a legitimate Roblox site?

No, it is a fraudulent phishing page hosted on github.io and is not affiliated with Roblox. The official domain for Roblox is roblox.com.

What happens if I entered my password on chahinekallouch30-bot.github.io?

The page captures your username and password, giving attackers direct access to your account. You should log into roblox.com immediately to change your password and review linked account settings.

How can I tell this is a fake Roblox login?

The URL uses chahinekallouch30-bot.github.io instead of the official roblox.com address. Independent security tools have flagged it, as flagged by urlscan and 7 VirusTotal engines.

Explore

Blocklist matches1 external + PhishDestroy list · OpenPhish · PhishDestroy 1
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Page captures (2)

All capture links and hashes (2)

Domain details

Domain
IP Context 185.199.108.153 GitHub Pages shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub
Abuse contactabuse@github.com
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://chahinekallouch30-bot.github.io/Roblox.com
TLS Certificate
Issued by YR1 · stored validity ends in 37 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.108.153
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Nameservers 8

  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • dns4.p05.nsone.net
  • ns-1339.awsdns-39.org
  • ns-1622.awsdns-10.co.uk
  • ns-393.awsdns-49.com
  • ns-692.awsdns-22.net

TLS certificate

Issuer
YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

VirusTotal Analysis

7 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
G-Data
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of chahinekallouch30-bot.github.io ·

100
Good
Performance
FCP
0.8 s
First Contentful Paint
LCP
0.8 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.8 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data70
Open complete records

Captured network requests

Network requests: 3 SHA-256 hashes: 3 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:30 UTC.

Open this scan on URLScan 01a203de-de0d-7374-9906-7b4004c29b30 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations0

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

No retained observations are recorded.

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    chahinekallouch30-bot.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Forensic Evidence Collected recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+5006 d 4 h
  3. Added to PhishDestroy+15 h 22 min
  1. Added to PhishDestroy

    chahinekallouch30-bot.github.io

    same minute
  2. URLScan

    Page captured

    +15 h 22 min
  3. VirusTotal

    7/92 engine detections

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

chahinekallouch30-bot.github.io

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including chahinekallouch30-bot.github.io)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/chahinekallouch30-bot.github.io"
  title="PhishDestroy threat report for chahinekallouch30-bot.github.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>