VirusTotal
1 / 91 engine detections
レポートを開く“Access Restricted — connectIPS”
フィッシング: conneecttippsverify.live — コンテンツが利用できません. 証拠の概要: VirusTotal 1/91 (Fortinet); Spamhaus DBL_SPAM; PhishDestroy score 71/100. レジストラ: Name.com.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 91 engine detections
レポートを開くSuspicious
レポートを開くDBL_SPAM
Scan report
レポートを開く4 community references
レポートを開く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
conneecttippsverify.live is on the PhishDestroy blocklist as a suspicious domain borrowing the connectIPS name. Its page carried the title "Access Restricted — connectIPS", and the domain is a misspelling of the brand padded with the word "verify". PhishDestroy first saw it on 2026-10-05. It has been offline since 2026-10-06, and its DNS was still inactive when last checked on 2026-10-19.
The page title shows the site presenting itself as connectIPS and telling visitors their access is restricted. A warning like that, on a misspelled domain built around "verify", is a common way to push people to confirm their identity in a hurry. The likely risk is that a visitor types connectIPS login details, one-time codes or other account information into a page the brand does not control. Anything entered there should be treated as exposed.
Independent detection is thin. On 2026-10-06 only Fortinet flagged the domain, 1 of 91 VirusTotal engines. Spamhaus lists it in its DBL with a spam classification. Four AlienVault OTX pulses reference it, so other researchers have also tracked it. The case rests on the brand misuse in the page title and the lookalike name more than on broad scanner consensus.
The domain was registered through Name.com, Inc. on 2026-10-04, one day before PhishDestroy saw it. It was hosted on Amazon.com, Inc. network space in the US at 216.150.1.193. It went dark by 2026-10-06, so the whole visible lifespan was about two days. That short run fits a throwaway domain rather than a real service. The Let's Encrypt certificate gave the page a padlock, but that only means the connection was encrypted. It says nothing about who ran the site.
If you entered a connectIPS username, password or PIN on this site, change them right away through the official connectIPS app or website. Then check your account for logins, linked accounts or payments you don't recognise. If you shared a one-time code, contact your bank and connectIPS support so they can watch for misuse. Going forward, reach the service only by typing its address yourself or through the official app, never through a link in a warning message. Defenders should block the domain and its IP, search mail and proxy logs for lookups from 2026-10-04 onward, and alert users who may have reached the page.
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.
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.
Edge-IP の評判はこのドメインに起因しません。
ns1.vercel-dns.comns2.vercel-dns.comLocation describes the IP network.
a9bffc280b2a2322adcd4e9e5022dee6f11137395f3f8dd2e620510b86b54207Saved 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 conneecttippsverify.live · checked Oct 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→inactive
http_no_content
到達可能→利用不可
到達可能
1/91 engine detections
View source4 community references
View sourceNo threat flag
View sourcePD-20261005-266D66
conneecttippsverify.live
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
conneecttippsverify.live
PD-20261005-266D66 Recipient: abuse@name.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
conneecttippsverify.live)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.