xulvertik.digital returned HTTP status 200 in an HTTP check dated 2026-10-01, the most recent recorded observation for this domain. The domain was first observed on 2026-09-20 and was registered through Spaceship, Inc. on 2026-05-31.
Recorded Evidence
An HTTP check dated 2026-10-01 recorded status 200 for xulvertik.digital. VirusTotal, checked on 2026-10-01, reported 17 detections across 91 scanners. OTX, checked on 2026-09-21, listed 3 pulses. The domain was first observed on 2026-09-20, and its registration date was 2026-05-31 with registrar Spaceship, Inc. The IP address 185.62.57.28 is recorded in the Netherlands under the organization Snel. PhishDestroy's internal listing was recorded as true, and the blocklist check date was 2026-10-01.
Interpretation
The recorded sources describe different aspects of xulvertik.digital rather than a single measurement. The HTTP status, VirusTotal detections, OTX pulses, and PhishDestroy listing each come from separate checks, so they should be read as distinct observations. The chronology from first observation to the later checks provides a sequence, but the exact dates alone do not show a trend or change in behavior.
Recommended Actions
For xulvertik.digital, preserve the HTTP check record, the VirusTotal result, and the OTX pulses as separate source records. Compare the PhishDestroy listing against the other source records to see whether they align. Review the recorded HTTP status alongside the detection counts before deciding on any further action.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttp://xulvertik.digital/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
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-13 22:16:00 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:36 UTClast content: 2026-10-13 22:16:00 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.
VirusTotal Detections Update2026-09-21 16:02:13 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.62.57.28.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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
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)
