> For the complete documentation index, see [llms.txt](https://fraudhuntertw.gitbook.io/fraudhuntertw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fraudhuntertw.gitbook.io/fraudhuntertw/identify/02-identify.md).

# 識別技巧總覽

![識別技巧總覽](/files/OGljxuyzvUcEUmMuxnWz)

第 1 篇教你「停・查・問」的心法，這一篇講的是怎麼「查」：當你停下來之後，怎麼在幾秒鐘內看破對方是真是假。

這一篇分成六個主題，順著詐騙接觸你的流程走，從「對方怎麼找上你」一直到「最後怎麼把錢拿走」：

![六個識別面向總覽](/files/HprShsh5iYB1yS1mVcuw)

| 章節                                                        | 一句話重點                    |
| --------------------------------------------------------- | ------------------------ |
| [網址 / 連結識別](/fraudhuntertw/identify/url.md)               | 看網域、看相似字、別被「鎖頭」騙了        |
| [Email 寄件者識別](/fraudhuntertw/identify/email.md)           | 顯示名稱可以亂取，看「真實寄件地址」       |
| [簡訊 / 電話識別](/fraudhuntertw/identify/sms-phone.md)         | +886 回撥、未知短碼、官方不會用簡訊連結辦事 |
| [社群帳號 / 賣家識別](/fraudhuntertw/identify/social-account.md)  | 盜帳號、假 profile、零評價、私訊轉帳   |
| [假 App / 假網站識別](/fraudhuntertw/identify/fake-app-site.md) | 誘導安裝 APK、描述檔、一頁式購物網      |
| [付款方式紅旗](/fraudhuntertw/identify/payment-redflags.md)     | 最強照妖鏡：怎麼付錢，決定了它是不是詐騙     |

> 如果你只想學一招，建議直接看最後一章〈[付款方式紅旗](/fraudhuntertw/identify/payment-redflags.md)〉。不管詐騙包裝得多漂亮，它最後一定得把錢從你的口袋移到他的口袋，而能用的金流手法就那幾種。認得付款方式的紅旗，幾乎就能反推出整件事是不是詐騙。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fraudhuntertw.gitbook.io/fraudhuntertw/identify/02-identify.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.