Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@registrar.eu.
The latest stored availability evidence still shows the domain reachable; 2 days 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.
relay-fr-me[.]com
relay-fr-me.com — 未验证. 证据摘要: VirusTotal 17/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, ESET); URLQuery 3 alerts; Spamhaus DBL_PHISH; CF Radar malicious; PhishDestroy score 100/100. 注册商: Hosting Concepts.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
Assessment
Stored evidence for relay-fr-me.com: VirusTotal recorded 17 detections among 91 scanners on 2026-08-12. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for relay-fr-me.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 17 detections among 91 scanners in the stored snapshot dated 2026-08-12. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-12 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for relay-fr-me.com in the snapshot dated 2026-08-12. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains relay-fr-me.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed relay-fr-me.com on 2026-08-11. The OpenPhish blocklist snapshot is dated 2026-08-12 and remains a separate event in the stored timeline. A stored HTTP status 302 was observed for relay-fr-me.com on 2026-08-12. The HTTP status 302 dated 2026-08-12 records a single response for later comparison. The registration date is separately recorded as 2026-08-07. A URLScan reference was stored on 2026-08-11 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 45.74.47.181 as the observed address in this record. The registration date for relay-fr-me.com is recorded as 2026-08-07. The observed server header is recorded as nginx in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The relay-fr-me.com record states that VirusTotal recorded 17 detections among 91 scanners on 2026-08-12. OpenPhish remain named blocklist observations from the snapshot dated 2026-08-12. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 45.74.47.181. The supported conclusion is bounded to the exact stored observations for relay-fr-me.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to relay-fr-me.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain relay-fr-me.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to relay-fr-me.com. The stored record does not justify extending that rule to 45.74.47.181 or to other infrastructure records.
网络安全情报
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | relay-fr-me.com |
malicious | Sinkholed |
| OpenDNS | relay-fr-me.com |
phishing | Phishing Block |
| Cloudflare DNS | relay-fr-me.com |
malicious | Sinkholed |
威胁响应 Pipeline
公共封禁名单状态
已保存的截图
域名情报
技术细节DNS、SSL SAN、时间戳
ICANN OVERSIGHT
认证和 RAA 背景
认证和 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.
所用技术 · 2 identified
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
nginx.org 置信度 100%VirusTotal 分析
网站性能分析
Google PageSpeed Insights — mobile performance audit of relay-fr-me.com · checked Aug 11, 2026
证据与外部报告
PD-20260811-058461 Recipient: abuse@registrar.eu 您是否受到本网站的影响?
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。