bluebadgeteamcheck.vercel.app returned HTTP status 451 in an HTTP check recorded on 2026-10-01, the most recent status observation in this evidence set. The same domain was first observed on 2026-09-17, and the PhishDestroy internal listing was recorded as true.
Recorded Evidence
The PhishDestroy internal listing for bluebadgeteamcheck.vercel.app was recorded as true. A VirusTotal scan dated 2026-09-23 reported 17 detections across 89 scanners. An SSL scan on 2026-09-23 named the certificate issuer as Google Trust Services / WR1. The domain resolved to IP address 64.29.17.131, held by Vercel, Inc in the United States. The HTTP check on 2026-10-01 returned status 451.
Interpretation
The PhishDestroy listing and the VirusTotal detection count are separate source records, so a reader should weigh them as distinct observations rather than one combined signal. The first-observed date and the HTTP check date frame a window in which the domain was catalogued and later returned a 451 response, but those records do not establish present availability. The SSL scan and VirusTotal scan share a calendar date, yet a shared date does not show that the two measurements were taken at the same moment or that their results are directly comparable.
Recommended Actions
Preserve the PhishDestroy listing record and the VirusTotal scan result for bluebadgeteamcheck.vercel.app as separate source artifacts, and compare them against any later observations of the same domain. Retain the HTTP check record alongside the first-observed entry so the sequence of recorded status observations can be reviewed. If further checks are performed, capture them with explicit timestamps and keep each source result distinct rather than merging them into one summary.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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-17 14:28:09 UTCcurrent episode first observed: 2026-10-01 01:55:00 UTCobserved RIP window: 2026-09-17 14:28:09 UTC → 2026-10-01 01:55:00 UTC · 323.45hmidpoint estimate ≈ 2026-09-24 08:11:34 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.
기술 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
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.
Domain ingestion complete. Initial state is marked as alive.
위협 대응 Pipeline
발견
Analysis
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
위협 탐지됨
bluebadgeteamcheck.vercel.app 탐지되어 전체 분석을 위해 대기열에 추가됨
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.
Web Archive
Preserved in 웨이백 머신 — historical evidence archived
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
2026년 9월 24일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 152 시간이 경과되었습니다.
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+
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.
(US)
