axiom.cnhima.com was observed with a ScamSniffer blocklist entry dated 2026-10-11, documenting its inclusion in a security intelligence source. The domain also appeared in an internal listing from PhishDestroy on the same date, providing additional context for its monitoring status.
Recorded Evidence
On 2026-10-11, ScamSniffer recorded axiom.cnhima.com on its external blocklist. PhishDestroy internally listed the domain as of that date. The SSL certificate for axiom.cnhima.com was issued by Let's Encrypt / YE2 and scanned on 2026-10-11, confirming technical infrastructure details.
Interpretation
The ScamSniffer entry records a blocklist detection, which catalogs domains for security review based on external intelligence. PhishDestroy's internal listing documents another form of monitoring, offering a distinct perspective on the domain's profile. These sources together provide a snapshot of axiom.cnhima.com in both external and internal security contexts, with each record representing a specific type of observation.
Recommended Actions
Preserve the ScamSniffer blocklist entry and the PhishDestroy internal listing for axiom.cnhima.com as reference points for future assessments. Compare these records to any subsequent observations to monitor changes in security intelligence listings for the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
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: StaleRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 11:02:01 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 11:02:01 UTClast content: 2026-10-11 11:02:01 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 08:31:50 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 132.243.225.155.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
7 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.
(DE)
