ABUSE NOTICE · 7D+ 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@omegatech.sc.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
DOM Analysisanalyzed 2026年9月11日score 100/1001 brand signal
Submitted URLhttp://paylifeat-info.com/
Favicon Hash
案件 ID
页面标题
Google
Impersonates
Google
TLS 证书
Certificate hostname mismatch·
颁发者 Let's Encrypt / YR1· stored validity ends in 54 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
158.94.208.88
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Frankfurt am Main, DE
Server header
gws
域名服务器 2
ns1.vercel-dns.com
ns2.vercel-dns.com
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YR1
Valid from
2026-09-08 16:29:38
Valid until
2026-12-07 16:29:37
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:59 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8c507ab8289bbf6bfc6082ea8efa5315aebcc6c35f70999c9aa5217ceaaa1368Certificate names · 1 SANs
zen-roentgen.158-94-208-88.plesk.page
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:08:45 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:08:45 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: 11 detections
alphaMountain.ai
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Netcraft
SOCRadar
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of paylifeat-info.com· checked Sep 11, 2026
86
Needs Work
Performance
FCP
1.69s
First Contentful Paint
LCP
1.85s
Largest Contentful Paint
CLS
0.023
Cumulative Layout Shift
TBT
511ms
Total Blocking Time
SI
1.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-09-11 03:41:06 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 158.94.208.88.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
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)
