An HTTP request to bitbdiuigegienn.gitbook.io on 2026-10-01 returned status 403, a dated response recorded alongside a first observation of 2026-09-11. The same record set notes an internal listing on the PhishDestroy list, which is a separate signal from the HTTP response.
Recorded Evidence
The domain was first observed on 2026-09-11, the date of its SSL scan and PageSpeed check, which produced a performance score of 64. An HTTP check on 2026-10-01 returned 403, while VirusTotal on 2026-09-13 reported 14 detections across 89 scanners. External blocklists MetaMask and SEAL were counted on 2026-10-01, the same date as the HTTP check.
Interpretation
The VirusTotal detections and the two external blocklist entries are separate source records, each with its own scope and timing; they are not combined here into a single judgment. The first observation, SSL scan and PageSpeed check share the date 2026-09-11, while the VirusTotal check and the HTTP and blocklist checks fall on later dates, so the records span more than one measurement point. The 403 response describes only the recorded request, not all content the domain may serve.
Recommended Actions
For bitbdiuigegienn.gitbook.io, preserve the VirusTotal record and the external blocklist entries as separate source artifacts for later comparison. Compare the HTTP response record against the internal listing to see whether the two sources align over time. Retain the PageSpeed and SSL scan records alongside the first-observation entry so the earliest available measurements remain traceable. Recheck the domain against the same named sources before acting on any single record.
Registration (base domain)gitbook.io · 생성됨 2014년 3월 30일
HTTP 상태403 Forbidden
Elapsed Since First Report3 days
집계 기준
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 연결 가능 · 액세스가 제한됨.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 11일
DOM Analysisanalyzed 2026년 9월 11일score 80/1001 brand signal
Submitted URLhttp://bitbdiuigegienn.gitbook.io/
Favicon Hash
Observed page title
Bitbuy Login: Unlocking Your Access to the Crypto Universe | us
Automated brand references
Ethereum
TLS 인증서
발급자 Google Trust Services / WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.64.147.209
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
네임서버 1
hugh.ns.cloudflare.com
Location describes the IP network.
TLS 인증서
Issuer
Google Trust Services / WE1
Valid from
2026-07-17 18:03:25
Valid until
2026-10-15 19:03:12
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-11 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464adCertificate names · 1 SANs
gitbook.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-13 22:05:23 UTCcurrent episode first observed: 2026-10-01 01:39:21 UTCobserved RIP window: 2026-09-13 22:05:23 UTC → 2026-10-01 01:39:21 UTC · 411.57hmidpoint estimate ≈ 2026-09-22 11:52:22 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 6 identified
G
GitBook
Documentation
GitBook is a command-line tool for creating documentation using Git and Markdown.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
지금 당장 어떻게 해야 할까요?
긴급
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 bitbdiuigegienn.gitbook.io)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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.
