VirusTotal
8 / 91 engine detections
打开报告“Replug - A complete link marketing platform”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hetzner.com.
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.
钓鱼: mylinkinb.io — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 8/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, Lionic); URLQuery 3 alerts…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
8 / 91 engine detections
打开报告3 threat-system alerts
打开报告18 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mylinkinb.io is an impersonation phishing page that presents itself under the title "Replug - A complete link marketing platform." Its likely targets are marketers, creators and small businesses who use link-shortening and link-in-bio tools. PhishDestroy first flagged it on 2026-09-19, and it was still online with live content on 2026-10-19. The page title points to a legitimate link marketing service, while our classification is impersonation phishing.
Impersonation pages copy the look and wording of a trusted service so visitors believe they are on the real login or signup screen. Here the Replug branding gives people who manage campaign links a familiar place to enter their email, password or connected social and payment accounts. Anything typed into the form goes to the operators. A hijacked link marketing account lets them redirect a victim's audience to malicious destinations, harvest contacts or reuse the same password on other services.
Eight of 91 VirusTotal engines flagged the domain as of 2026-09-29: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar and VIPRE. That is a modest count, but it comes from independent vendors that use different detection methods. The domain also appears in 18 AlienVault OTX pulses, so other researchers have tracked it as well. PhishDestroy lists it on its own blocklist.
The domain was registered on 2020-02-13 through Namecheap, more than six years before we detected it. A domain that old can slip past filters that distrust new registrations. It resolves to 49.12.20.10 on Hetzner Online GmbH's network in Germany. The Let's Encrypt certificate only means the padlock appears in the browser, which says nothing about whether the site is legitimate.
If you entered credentials on mylinkinb.io, change that password at once on the genuine service and on any other account where you reused it. Turn on two-factor authentication. Check your link marketing account for redirects you did not create, new team members or changed payment details, and revoke unfamiliar connected apps or sessions. Defenders should block the domain and its IP at DNS and proxy level, and search mail and web logs for users who visited it.
Edge-IP 声誉不属于此域。
bill.ns.cloudflare.comnola.ns.cloudflare.comLocation describes the IP network.
6e8a8dd0e9418e9cb1b8a3423d2eebdb28c26378e6c04425bb9b05847cd6d9e7Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of mylinkinb.io · checked Sep 19, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
mylinkinb.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
9→10
No threat flag
View source8/91 engine detections
View source18 community references
View sourcePD-20260919-9F4B2C
Page captured
View sourcemylinkinb.io
View sourcePD-20260919-9F4B2C Recipient: abuse@hetzner.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
mylinkinb.io)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.