Link and intent signals
Checks can look for suspicious URL structure, brand-domain mismatch, urgency, OTP/UPI pressure, fake authority, and other common scam patterns.
What the public scanner checks
For submitted text and links, the live service combines deterministic signals with enrichment and, when available, AI-assisted analysis. The exact signals used depend on the input and service availability.
Threat reputation evidence
Known URL/domain evidence is checked against the available historical reputation index and published threat-intelligence enrichment before live AI analysis is needed.
Service-aware analysis
When an external analysis provider is unavailable, VerifyPulse does not treat the lack of analysis as proof that content is safe.
Privacy and data-practice boundaries
Please do not submit OTPs, PINs, passwords, card details, bank-account credentials, or other unnecessary sensitive information. Use an official bank or service channel for account-specific issues.
Input safeguards
The public verification route applies supported-type and input-size checks. External file analysis requires an explicit consent signal before it begins.
B2B metadata-only events
The current B2B scan route emits structured operational events that exclude raw scan content, URLs, API keys, IP addresses, contact data, credentials, and personal identifiers.
Controlled API access
The B2B URL-scan route includes API-key authentication, scope checks, browser-origin allow-listing, correlation IDs, and basic request-rate controls.
Important limitation
These controls are not an external security certification. Prospective business customers should perform their own review before processing customer information.
How we reduce avoidable risk
Evidence is shown with the result
Where available, results explain the decision basis—for example, historical reputation evidence, URL/intent signals, model-assisted analysis, or service status.
Uncertainty is not hidden
If the service cannot complete live analysis and there is no strong local evidence, the result should recommend independent verification rather than saying SAFE.
Important files are integrity checked
Critical implementation and data files are checked against an integrity manifest to help detect unreviewed changes in the maintained repository.
Known limits are stated
VerifyPulse does not currently replace a bank’s fraud engine, transaction controls, device intelligence, human investigation process, or final payment decision.
Decision boundary: Never use a VerifyPulse result as the only reason to send money, share credentials, unblock an account, or automatically block a customer transaction. Use the claimed organisation’s official app, website, or support channel to confirm sensitive requests.
For business and security enquiries
For a controlled business-pilot discussion, review the Pilot page. For a security concern or correction to this page, contact narayanglokhande2007@gmail.com. Responsible disclosure details are also published at /.well-known/security.txt.