VirusTotal
17 / 91 engine detections
レポートを開く“Trinity Fellowship Addis Ababa”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@cosmotown.com.
The latest stored availability evidence still shows the domain reachable; 28 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.
フィッシング: trinityfellowshipaddis.org — 最後に確認されたアクティブな状態 (HTTP 307). 証拠の概要: VirusTotal 17/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 91 engine detections
レポートを開く3 det.
レポートを開く悪意あり
レポートを開く5 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
trinityfellowshipaddis.org presents itself as "Trinity Fellowship Addis Ababa" and borrows the name and identity of that fellowship to win the trust of its members, supporters and anyone searching for it. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-23. As of 2026-10-19 the domain was still live and redirecting visitors elsewhere, so it remains an active risk.
Impersonation pages copy the look and name of a trusted organisation, here a faith community, so that visitors lower their guard. Once trust is established, these sites typically ask for personal details, login credentials or payments presented as donations, offerings or membership fees, and that money or data goes to the operators instead of the real fellowship. The redirect means the page a visitor finally lands on can be swapped at any time, so what one person sees may differ from what the next person is shown.
Seventeen of 91 VirusTotal engines flagged the domain as of 2026-10-02. The vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. Agreement across that many unrelated vendors makes a false positive unlikely. The domain also appears in five AlienVault OTX threat pulses, meaning other researchers have tied it to malicious activity, and it is listed on the PhishDestroy blocklist.
The domain was registered on 2026-02-24 through TuringSign Inc. d/b/a Cosmotown, roughly seven months before PhishDestroy detected it. That gap suggests the name was held quietly before being put to use. It resolves to 216.198.79.1 on Amazon.com, Inc. infrastructure in the US. Its Let's Encrypt certificate gives the site a padlock icon, which shows only that the connection is encrypted and says nothing about who runs the page.
If you sent money through this site believing it was a donation or fee to Trinity Fellowship, contact your bank or payment provider right away to dispute the charge. Confirm any request directly with the fellowship through contact details you already know. If you entered a password, change it everywhere you reused it and turn on two-factor authentication. Watch for follow-up messages that use your details to look convincing. Defenders should block the domain and its IP at DNS and proxy level, and the genuine fellowship should warn its community about the lookalike.
Stored page, network and scanner observations, grouped by source and observation time.
観測された: · Retrieved:
| Uuid | 01a0cd82-166a-71ac-9254-72390c30e0e7 |
|---|---|
| Final url | https://www.trinityfellowshipaddis.org/ |
| ステータス | 200 |
| リダイレクト | parent-domain |
| Redirects | [
{
"to": "https://trinityfellowshipaddis.org/",
"from": "http://trinityfellowshipaddis.org/",
"status": 307
},
{
"to": "https://www.trinityfellowshipaddis.org/",
"from": "https://trinityfellowshipaddis.org/",
"status": 307
}
] |
| Ip | 216.198.79.1 |
| Contacted domains | [
"trinityfellowshipaddis.org"
] |
| Contacted IP addresses | [
"216.198.79.1"
] |
| Asns | [
"16509"
] |
| Countries | [
"US"
] |
| Document hash | b82549bd0a5474245bff92d0a00affbf4c980f10ae8d5afee7a19c4f40bbc08f |
| Script hashes | [
"7e00fe30926e1fd2d1077b38c5083d6446b80fb826435be4283f33db8eaff6fe",
"bbc0826384faf59b3d35a439a95f7787cd19280ee35469c84cd0b213bc306f11",
"fd13288643289ee2e4fb15a1b6672a675d05937de623ce52d87c0c3e247db00f",
"992c17dff8cf934069c65dbfc66bc50ad65f81b7ed249c9aa89981daff8d6d42",
"8215fe5a9b24150f63a7702de6e70ad9e908f50131bcf3822059d2abb2d026a3",
"69ed125a595447e1310e2070706410e6fffef9ed27827ea049c3755110ac3320",
"b28d7a016cd831df32919624ec9d6a9657db51400307cdb0bf7a6fd96e99d1c6",
"a1ce386c6ccba0cab97932c84e4e428441be846eac2cc681f71f5eb384b478e3",
"e9786b1305894e4119bb9811a816dac9cf576755596dd989ee15b455749fc35e",
"a6248517cd3ee53a8186b51c59e1e764e3dc0c512f4acbd50e818f9884663e21"
] |
| Globals | [
"TURBOPACK",
"__next_f",
"next",
"__webpack_hash__",
"_N_E_STYLE_LOAD",
"MotionIsMounted",
"vam",
"va",
"vaq",
"vai"
] |
| Storage keys | [
"lswt-0.233147677041290250.8019878374877509"
] |
| Tls | {
"san": [
"www.trinityfellowshipaddis.org"
],
"cipher": "AES_128_GCM",
"issuer": "YR1",
"subject": "www.trinityfellowshipaddis.org",
"protocol": "TLS 1.3",
"valid_to": "2026-11-27T21:38:08Z",
"valid_from": "2026-08-29T21:38:09Z"
} |
| Domain age days | 148 |
| Apex age days | 210 |
| Tls age days | 24 |
| Tls valid days | 89 |
| Requests | 22 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 60,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Vercel",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=63072000"
} |
観測された: · Retrieved:
| Uuid | 4b79ee98-e914-44a0-b311-85db182ac1c7 |
|---|---|
| Final url | https://www.trinityfellowshipaddis.org/ |
| ステータス | 200 |
| リダイレクト | subdomain |
| History | [
{
"url": "https://trinityfellowshipaddis.org/",
"status": 307
},
{
"url": "https://www.trinityfellowshipaddis.org/",
"status": 200
}
] |
| DOM structure hash | 69995d891433c60ad14643f57b0d56624c9d1b4f2fd288a799354af812314a38 |
| Document hash | b82549bd0a5474245bff92d0a00affbf4c980f10ae8d5afee7a19c4f40bbc08f |
| Domain risks | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "trinityfellowshipaddis.org",
"type": "A",
"value": "216.198.79.1"
},
{
"name": "www.trinityfellowshipaddis.org",
"type": "CNAME",
"value": "ab3b302ebdd40c15.vercel-dns-017.com"
},
{
"name": "www.trinityfellowshipaddis.org",
"type": "CNAME",
"value": "ab3b302ebdd40c15.vercel-dns-017.com"
}
] |
| Dnssec valid | false |
| Ip | 64.29.17.65 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"created": "2026-02-24T13:42:55Z",
"updated": "2026-08-11T23:20:00Z",
"expires": "2027-02-24T13:42:55Z",
"nameservers": [
"bob.ns.cloudflare.com",
"sreeni.ns.cloudflare.com"
]
} |
Edge-IP の評判はこのドメインに起因しません。
bob.ns.cloudflare.comsreeni.ns.cloudflare.comtrinityfellowshipaddis.orgpriority 0Location describes the IP network.
63698e07f6ea369d00598f219ee79a7f0dbf467b871b671a3a193a1bd548bee2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.trinityfellowshipaddis.orgDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of trinityfellowshipaddis.org · checked Sep 23, 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.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
到達可能
No threat flag
View source17/91 engine detections
View source5 community references
View sourcePD-20260923-DC34D1
Page captured
View sourcetrinityfellowshipaddis.org
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
trinityfellowshipaddis.org
PD-20260923-DC34D1 Recipient: abuse@cosmotown.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 ↗
trinityfellowshipaddis.org)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.