일치를 보고하는 공개 차단 목록: 2. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 24 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
24 hours
Reports sent
1
Latest case ID
PD-20261010-6E675B
Current status
HTTP 200 at latest stored check
보고서 요약
xn--b4caub.cc — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: MetaMask; 사기 유형: Impersonation. 증거 요약: Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 90/100. 등록기관: DYNADOT.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
The domain xn--b4caub.cc was observed with a PhishDestroy internal listing on 2026-10-10, providing a dated record of its status. On the same date, the domain was also noted to have entries on two external blocklists, which offers additional context for its security profile.
Recorded Evidence
MetaMask and SEAL each recorded blocklist entries for xn--b4caub.cc on 2026-10-10. PhishDestroy listed the domain internally on that date as well. The domain was registered on 2026-10-06 through DYNADOT LLC.
Interpretation
PhishDestroy contains an internal listing for xn--b4caub.cc, documenting its inclusion in their database as of 2026-10-10. MetaMask and SEAL each provide external blocklist records, which reflect their own detection criteria and add to the breadth of sources. These records together describe the domain’s presence across multiple independent security intelligence systems.
Recommended Actions
For xn--b4caub.cc, preserve the MetaMask and SEAL blocklist records as evidence for ongoing monitoring. Retain the PhishDestroy internal listing for comparison with future source entries. Use these documented records to inform any future assessments or reviews involving this domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
등록 정보생성됨 2026년 10월 6일 (5d · Brand New!)—Expires 2027년 10월 6일
HTTP 상태200
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 10일
DOM Analysisanalyzed 2026년 10월 10일score 90/100
Submitted URLhttp://xn--b4caub.cc/
Favicon Hash
사건 ID
페이지 제목
澳门新葡京
TLS 인증서
Certificate hostname mismatch·
발급자 Let's Encrypt / YE2· stored validity ends in 84 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
91.92.243.106
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Rotterdam, NL
Server header
openresty_edge
네임서버 2
n1.xundns.com
n2.xundns.com
Location describes the IP network.
TLS 인증서
Issuer
Let's Encrypt / YE2
Valid from
2026-10-06 14:08:27
Valid until
2027-01-04 14:08:26
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-10 16:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint826b7ec32826e2e68265412c23d27b2c4fb419d51ffd1e559719a4c2996f33d5Certificate names · 1 SANs
www.xn--b4caub.cc
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:00:21 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:21 UTClast content: 2026-10-11 10:00:21 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.
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-10 14:03:25 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 91.92.243.106.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
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)
