Trunk provisioning
SIP URI validator & routing preview
Validate SIP URI formatting before trunk deployment. Parses scheme, user, host, port, and parameters. Shows which DNS records (SRV, NAPTR/ENUM) would be queried for routing.
Examples
Parsed components
- scheme
- sip
- user
- 1001
- host
- pbx.example.com
- port
- 5060
DNS routing preview
Live DNS resolution coming soon. These are the records that would be queried:
- SRV
_sip._udp.pbx.example.com
UDP SIP service discovery (default)
- SRV
_sip._tcp.pbx.example.com
TCP SIP service discovery
- A/AAAA
pbx.example.com
Direct host resolution if no SRV records
How it works
Three steps to results
- 01
Enter a SIP URI
Paste or type a SIP URI like sip:+15551234567@carrier.example.com:5060 or sips:trunk@pbx.local. The validator checks RFC 3261 syntax including IPv4, IPv6, and tel: URIs.
- 02
Review parsed components
See the URI broken into scheme, user, password, host, port, parameters, and headers. Validation errors are shown with specific remediation hints.
- 03
Preview DNS routing
For domain-based URIs, see which SRV records (_sip._udp, _sips._tcp) and NAPTR/ENUM queries would be needed. Live DNS resolution coming soon.
FAQ
Frequently asked questions
Common questions about this tool and how it fits into your VoIP security workflow.
Contact support →Paste the URI into this validator. It checks scheme (sip/sips/tel), user part, host format (FQDN, IPv4, or bracketed IPv6), port range, and parameter syntax per RFC 3261.
Related tools
More free VoIP utilities
Trunk configured?
Protect your SIP trunks from real-time attacks.
SipRadar's global blacklist blocks known toll-fraud infrastructure before it reaches your carrier peers. Pull the feed via API or plain-text.