The domain bnbtokenmaker.com was recorded with a PhishDestroy internal listing on 2026-10-13, and a PageSpeed performance score of 86 was also measured on the same date. The domain's registration date is documented as 2026-09-18.
Recorded Evidence
OTX contained four pulses referencing bnbtokenmaker.com as of 2026-10-13. VirusTotal checked the domain on 2026-10-03, recording 3 detections out of 92 total scanners. The registrar is Atak Domain, and the domain was first observed on 2026-10-13. PhishDestroy internally listed the domain on 2026-10-13.
Interpretation
PhishDestroy provides a listing record for bnbtokenmaker.com, documenting its presence in an internal catalogue. VirusTotal's measurement contains scanner-based detection counts, which are useful for comparing with other domains or future scans. The OTX record adds external intelligence context, showing the domain has been referenced in four pulses. These source records offer a snapshot of the domain's technical and intelligence profile as of their respective dates.
Recommended Actions
Preserve the PhishDestroy internal listing and VirusTotal detection records for bnbtokenmaker.com as reference points for future checks. Compare OTX pulse counts and PageSpeed performance scores with subsequent observations to monitor for changes. Use these dated records to inform ongoing review of the domain's security and technical profile.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
캡처 라우팅
Local보관됨 2026-10-13 13:41:11 UTC
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 11:40:27 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 11:40:27 UTC
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.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Fortinet
URLQuery
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of bnbtokenmaker.com· checked Oct 13, 2026
86
Needs Work
Performance
FCP
2.7s
First Contentful Paint
LCP
3.45s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
81ms
Total Blocking Time
SI
3.21s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:https://bnbtokenmaker.com/
BNB Token Maker — Create a BEP-20 Token on BNB Smart Chain
Create a BEP-20 token on BNB Smart Chain without writing Solidity. Configure the name, supply and contract controls, connect your wallet and deploy — non-custodial and ready in minutes.
Open Graph title:Create a BEP-20 Token on BNB Smart Chain | BNB Token Maker
Open Graph description:Create a BEP-20 token on BNB Smart Chain without writing Solidity. Configure the name, supply and contract controls, connect your wallet and deploy — non-custodial and ready in minutes.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
2 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 13:41:11 UTC
출처
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 13:41:11 UTC
출처
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-13 11:40:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.209.161.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
PDF notice generated Notice text archived (808 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (GB):
Computer Misuse Act 1990
Fraud Act 2006
Communications Act 2003 - Section 127
UK law criminalizes unauthorized computer access, fraud, and malicious communications.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(GB)
