Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
across-bridge.top returned HTTP status 502 on 2026-10-01, per the recorded HTTP check. The domain was first observed on 2026-09-02, and its registrar is listed as NICENIC INTERNATIONAL GROUP CO., LIMITED.
Recorded Evidence
VirusTotal recorded 8 detections across 89 scanners on 2026-09-13. OTX recorded 2 pulses on 2026-09-13, and the external blocklists MetaMask and SEAL were noted on 2026-10-01. The domain also appears in the phishdestroy internal listing, and the HTTP check on 2026-10-01 returned status 502.
Interpretation
The VirusTotal and OTX observations share the 2026-09-13 date, while the blocklist count and HTTP status were recorded on 2026-10-01, so these sources describe different moments and should not be treated as a single snapshot. The first observation on 2026-09-02 predates all of them, which means the later records can be compared against an earlier baseline rather than against each other directly.
Recommended Actions
Anyone reviewing across-bridge.top should retain the dated records from VirusTotal, OTX, the external blocklists and the HTTP check so later observations can be compared against them. Avoid submitting sensitive information while examining the domain, and treat the 2026-10-01 HTTP status as a dated response rather than a statement about current availability.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='across-bridge.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-12 10:47:30 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-12 18:17:36 UTCfirst terminal observation: 2026-09-12 18:17:36 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 First positive detection Previous stored snapshot: 6 detections
ChainPatrol
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
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.
VirusTotal Detections Update2026-09-13 02:35:13 UTC
VirusTotal scanner detections updated from 6 to 8. Added scanner alerts: Forcepoint ThreatSeeker, VIPRE.
Domain Status Transition2026-09-12 23:04:50 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
across-bridge.top 已检测到并排入队，待进行全面分析
2026年9月2日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年9月13日
Cloudflare Radar Report
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.
