phone-verification

Retrieve SMS verification codes from public or private numbers for authorized web security testing.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill phone-verification-dreadnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phone-verification
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/web-security/skills/phone-verification
Command: npx skills add https://github.com/dreadnode/capabilities --skill phone-verification-dreadnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authorized web security testers often need to receive SMS verification codes for signup, login, account recovery, or MFA testing workflows, but using personal phone numbers risks privacy exposure and can trigger blocks from target applications.

Core Features & Use Cases

  • Free Public Number Access: Retrieve temporary shared phone numbers from public services for low-risk testing scenarios.
  • Private Number Fallback: Escalate to paid private providers like Twilio when public numbers are blocked or rate-limited by target apps.
  • Inbox Management: Filter incoming messages by sender and poll for codes with configurable timeouts to reduce noise and wait times.
  • Use Case: When testing a new e-commerce platform's account recovery flow, use this skill to get a valid SMS code without linking your personal phone number to the test account.

Quick Start

Use the phone-verification skill to retrieve an SMS verification code for the target app's signup flow using a free public US phone number.

Frequently Asked Questions about phone-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get SMS verification codes for penetration testing without using my personal phone number?

Retrieve SMS verification codes for authorized penetration testing by using temporary shared phone numbers with inbox polling. This eliminates the need for personal phone numbers when testing signup, login, account recovery, and MFA flows.

What should I do when a target application blocks free public phone numbers during MFA testing?

When public numbers are blocked or rate-limited during MFA testing, escalate to private paid provider numbers via API key integration. This fallback ensures you can successfully complete SMS verification flows for authorized security assessments.

How can I filter incoming SMS messages to find my authentication code on a shared public number?

Filter incoming SMS messages by sender and poll the shared inbox for codes with configurable timeouts. This reduces noise and wait times when retrieving authentication codes from public phone numbers during security testing.

Can I use this for authorized red teaming of account recovery workflows?

Yes, authorized red teaming of account recovery workflows is supported. You can interact with target application SMS verification endpoints without exposing real user credentials or personal contact information.

Does SMS verification testing work with free public numbers for e-commerce platform assessments?

Free public US phone numbers are available for low-risk testing scenarios like e-commerce platform assessments. You can retrieve valid SMS codes for testing account recovery flows without linking a personal phone number to the test account.

What are the limitations of using shared public phone numbers for SMS verification testing?

Shared public phone numbers can be blocked or rate-limited by target applications, limiting their effectiveness. For reliable access during vulnerability assessments, private paid provider numbers via API key integration serve as a necessary fallback.