On this page

SMS & messages

What is smishing?

API · Pro

Coverage: Indicative result based on automatic signals, not sender verification. No result guarantees that a message is safe.

Open tool
On this page

Purpose

Smishing is deception by SMS that impersonates an organization to obtain money, information or codes. Check the sender, text and domain before acting; confirm requests through an official channel you already know.

Paste the text you received and we’ll instantly tell you whether it shows the typical signs of smishing: shortened links, domains imitating banks or couriers, and urgent pressure.

Requirements

Anyone can read these guides, no account needed. Some tools require Pro, as indicated in each guide.

Include the complete message. You do not need to open links or share personal codes.

How to use it

  1. Include the complete message. You do not need to open links or share personal codes.

  2. Check message

  3. Do not share passwords, PINs or verification codes in response to a text message.

  4. Check the link’s real domain: "bank-security.com" is not your bank’s website.

  5. Urgency ("final notice", "account blocked") is a scammer’s favourite tool.

  6. When in doubt, open the official website or app yourself instead of tapping the link.

Synthetic example

Note

Invented example, not a real lookup. Do not call or open its links.

Synthetic example
DHL: Last warning. Your parcel is blocked. Action required at https://parcel.example

Interpret the result

Don’t tap the link, don’t reply and don’t share any details. Delete it and, if unsure, contact the company through its official website or number.

It shows some scam signs. Don’t open the link; check directly on the official website or app.

Only domains are displayed, without active links. A familiar domain does not prove a message is genuine.

Limitations

Warning

The check runs in your browser: the message text is never sent to any server.

Indicative result based on automatic signals, not sender verification. No result guarantees that a message is safe.

Troubleshooting

Paste the message text to check it.

Use with the API

Warning

Needs an API key and credits. Each completed call costs 1 credit, even when there is no data. An active Pro account includes 20 credits per UTC calendar month, shared by every API route and spent first; unused monthly credits do not roll over. Credits bought on your account page work without Pro and never expire.

Note

Errors are never charged: 401 invalid_api_key (missing or invalid key), 403 pro_required (no Pro credits and no purchased credits), 422 invalid input, 429 quota_exceeded (no credits left), rate_limit_exceeded or ai_busy (the AI of sms-check is at capacity), 503 tool_warming (the data is still being prepared) or tool or provider unavailable. After a 429 or 503, retry once the seconds in the Retry-After header have passed.

Local rule-engine check of one SMS: scam, suspicious or likely safe, with the integer score behind it (4 or more scam, 2–3 suspicious, 0–1 likely safe), signals, hosts, link flags and the named brand with its sms-brand id.

Send the JSON body to the tool's own route, or to POST /v2/tools with the tool field added. Both routes return the same result.

Endpoint
POST https://api.nocall.io/v2/smishing
POST https://api.nocall.io/v2/tools  {"tool":"smishing","message":"CORREOS: su paquete está retenido. Pague urgente las tasas en https://correos-entrega.info/pago","country":"ES"}

Parameters

NameTypeRequiredDescription
messagestring (1–2000)YesSMS text to check.
countrystring (enum, 55)No (default: "ES")Country whose SMS rule set is used.
bash
REQUEST_ID="$(uuidgen)" && [ -n "$REQUEST_ID" ] &&
curl --request POST 'https://api.nocall.io/v2/smishing' \
  --header "Authorization: Bearer $NOCALL_API_KEY" \
  --header 'Content-Type: application/json' \
  --header "Idempotency-Key: $REQUEST_ID" \
  --data '{"message":"CORREOS: su paquete está retenido. Pague urgente las tasas en https://correos-entrega.info/pago","country":"ES"}'

Example response (200)

This is the documented example from the API reference. Lookups use a fictional number, and aggregates and AI answers show the shape of the result, not live data.

JSON
{
  "data": {
    "tool": "smishing",
    "result": {
      "verdict": "scam",
      "score": 9,
      "attention": true,
      "signals": [
        "suspicious_domain",
        "risky_tld",
        "urgency",
        "brand_impersonation",
        "delivery_lure"
      ],
      "hosts": [
        "correos-entrega.info"
      ],
      "linkFlags": [],
      "brand": "correos",
      "brandSlug": "correos"
    }
  },
  "meta": {
    "requestId": "req_example",
    "unitsCharged": 1,
    "usage": {
      "periodStart": "2026-10-01",
      "unitLimit": 20,
      "unitsUsed": 3,
      "unitsRemaining": 17
    }
  }
}

Result fields (data.result)

FieldTypeDescription
verdict"scam" | "suspicious" | "likely_safe"Verdict of the local rules.
scoreintegerInteger rule score: 4 or more is scam, 2–3 suspicious and 0–1 likely safe.
attentionbooleanWhether the content deserves a closer look.
signalsarray<string (enum, 10)>Rule signals that matched.
hostsarray<string>Host names found in the text.
linkFlagsarray<"http" | "userinfo" | "internationalHost" | "ipAddress" | "nonStandardPort">Structural warnings about the link: http, userinfo, international host, IP address or non-standard port.
brandstring | nullBrand named in the message, or null.
brandSlugstring (enum, 10) | nullThe sms-brand id of the named brand, or null.