cryptomarginova.com was observed with a blocklist record from MetaMask on 2026-10-11, documenting an external detection entry for that date. The domain also appears on another external blocklist, SEAL, as of the same day.
Recorded Evidence
MetaMask and SEAL both listed cryptomarginova.com on their external blocklists on 2026-10-11. PhishDestroy internally recorded the domain as listed, and the registrar is documented as Realtime Register B.V., with a registration date of 2026-08-13. The SSL certificate was issued by Amazon / Amazon RSA 2048 M04 and scanned on 2026-10-11.
Interpretation
PhishDestroy contains an internal listing for cryptomarginova.com, which records a specific type of detection relevant to its own monitoring scope. External blocklists such as MetaMask and SEAL provide additional context by documenting their own detection entries, which are separate from internal records. The evidence spans registration, certificate, and blocklist observations, allowing for comparison of technical and security-related data.
Recommended Actions
Preserve the blocklist records from MetaMask and SEAL for cryptomarginova.com to support ongoing security reviews. Retain the PhishDestroy internal listing as a reference point for internal detection history. Use the registration and SSL certificate details for technical context in future assessments.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
등록 정보생성됨 2026년 8월 13일 (59d · New)—Expires 2027년 8월 13일
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 11일
Submitted URLhttp://cryptomarginova.com/
사건 ID
TLS 인증서
Certificate hostname mismatch·
발급자 Amazon / Amazon RSA 2048 M04· stored validity ends in 178 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
54.192.35.117
네임서버 2
dax.ns.cloudflare.com
magnolia.ns.cloudflare.com
Location describes the IP network.
TLS 인증서
Issuer
Amazon / Amazon RSA 2048 M04
Valid from
2026-09-22 00:00:00
Valid until
2027-04-07 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 13:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdd98b3ce20457bfb3daadd76632c268cfb6ab50b36c9c6bbba26918be2f6f09eCertificate names · 9 SANs
capitalnexiva.com
cryptoallocen.com
cryptocreditova.com
cryptoequitra.com
cryptoledgoria.com
cryptovaultoria.com
cryptoyieldon.com
equityvanta.com
marketliquora.com
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-11 11:34:49 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 11:34:49 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-11 11:34:49 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 54.192.35.117.
위협 대응 Pipeline
발견
Analysis
Monitoring
5 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
