A SIP trunk provider reports that your PBX stopped answering keepalives, a remote office phone system cannot register, or you have just put a session border controller behind a new firewall and want to know whether it is visible from outside. VoIP problems are hard to narrow down because a SIP server that does not want to talk to you usually says nothing at all.
The SIP OPTIONS Diagnostic sends one SIP OPTIONS request from the NetTools.tech server to a SIP server you own, over UDP, TCP or TLS, and shows the response code, the server identification, the advertised methods and extensions, the timing and, for TLS, the certificate. Before the first test you prove control of the domain with a DNS TXT record.
What is SIP OPTIONS?
In simple terms
SIP, the Session Initiation Protocol, sets up, changes and ends multimedia sessions such as VoIP calls. It is used by IP phones, PBXs such as Asterisk or FreeSWITCH, proxies such as Kamailio, session border controllers and SIP trunk providers. The OPTIONS request asks a SIP server "what can you do?" without starting a call. The server answers with a status code, like HTTP, and usually lists the methods it allows and the extensions it supports.
Technical background
SIP is defined in RFC 3261. Messages are text with a start line, headers and an optional body. A request travels in a transaction, identified by the branch parameter of the top Via header together with Call-ID and CSeq. Responses have three-digit status codes:
| Class | Meaning | Examples |
|---|---|---|
| 1xx | Provisional | 100 Trying, 180 Ringing |
| 2xx | Success | 200 OK |
| 3xx | Redirection | 301, 302, 305 |
| 4xx | Client error | 401 Unauthorized, 403 Forbidden, 404 Not Found, 405 Method Not Allowed, 407 Proxy Authentication Required |
| 5xx | Server error | 500, 501 Not Implemented, 503 Service Unavailable |
| 6xx | Global failure | 603 Decline |
Conventional ports are 5060 for SIP over UDP or TCP and 5061 for SIP over TLS (sips: URIs), although real deployments often use others. Over UDP the client retransmits unanswered requests using Timer A, which starts at T1 = 500 ms and doubles. SIP also defines compact header forms: v for Via, f for From, t for To, i for Call-ID, m for Contact, l for Content-Length, k for Supported and others.
The OPTIONS response typically contains:
- Allow — the methods the server announces, such as INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER.
- Supported — option tags for extensions, such as
100rel(RFC 3262),timer(RFC 4028) orreplaces(RFC 3891). - Accept, Require, Unsupported — accepted body types and required or unsupported extensions.
- Server or User-Agent — the software, if the operator chose to disclose it.
Why use the SIP OPTIONS Diagnostic?
- See your SIP server from the internet. It shows what a trunk provider or a remote phone sees, not what works from inside the LAN.
- Separate "no SIP server" from "SIP server refuses me". A 401, 403 or 405 still proves that a SIP server answered; a refused TCP connection or an ICMP port unreachable says that nothing listens on that port.
- Compare transports. UDP, TCP and TLS often behave differently because of firewalls, NAT helpers (SIP ALG) and listener configuration.
- Check the TLS certificate on 5061. Expired, untrusted or wrongly named certificates are shown before any SIP request is sent.
- Review what the server discloses. The headers table shows whether the server announces its software version, methods and extensions.
Who should use it?
VoIP and telephony administrators running PBXs, SIP proxies or session border controllers, network engineers who manage the firewalls and NAT in front of them, and MSPs testing customer systems they are contracted and permitted to assess. It is not a scanner: only test SIP infrastructure you own or have explicit permission to assess.
How the SIP OPTIONS Diagnostic works
The browser sends the form to the NetTools.tech API. Authorization, DNS resolution and the SIP transaction happen on the NetTools server in Latvia, which uses its own small SIP client (no external SIP library).
- Validation. The target must be a hostname or an IPv4/IPv6 address. SIP URIs (
sip:,sips:), users (alice@…), passwords, angle brackets and parameters (;transport=tcp,?x=1) are refused. The port must be 5060, 5061 or a port from 1024 to 65535; other ports below 1024 belong to other services. An empty port means 5060, or 5061 for TLS. The timeout is 2, 4 (default), 6 or 8 seconds. - Authorization, checked again before every test.
- A hostname must be the verified domain or a subdomain of it.
- An IP address must be linked to the verified domain by DNS: one of the A/AAAA addresses of the domain or the SIP domain, or of the targets of its
_sip._udp,_sip._tcpor_sips._tcpSRV records. - The SIP domain used in the request URI must also be the verified domain or below it.
- The TXT record is looked up again. If it is gone, the verification falls back to pending and the test is refused.
- Alternatively, an IP address on the administrator allowlist (Admin → Settings → Integrations) can be tested without DNS verification. This is the only way to reach private networks; allowlist entries are IP addresses or ranges of at most /16 (IPv4) or /48 (IPv6).
- Address checks and pinning. Every address the hostname resolves to is checked. Private addresses are refused unless allowlisted; loopback, link-local (including cloud metadata addresses), multicast, broadcast, documentation and reserved space are never contacted, not even when allowlisted. A mix of public and blocked answers is refused as a whole. The connection then goes to the checked IPv4 address, so DNS cannot be changed between check and connection. The probe server has no IPv6 connectivity yet, so IPv6-only SIP servers are refused with an explanation.
- One OPTIONS transaction to
sip:<SIP domain>(TCP adds;transport=tcp, TLS usessips:<SIP domain>), with Via, Max-Forwards 70, a From header naming the NetTools diagnostic, To, Call-ID, CSeq1 OPTIONS, Contact,Accept: application/sdp, a User-Agent naming the NetTools diagnostic andContent-Length: 0. No Authorization header exists in the client.- UDP: at most two retransmissions, after 0.5 s and after another 1 s, and only while nothing has answered. An ICMP port unreachable is reported as connection refused.
- TCP: one connection, one request; the response is read from the stream by its Content-Length.
- TLS: TLS 1.2 or newer. The chain and the host name are validated after the handshake and before the request is sent; on failure the connection is closed and only the certificate is reported. Validation is never turned off to make a test succeed.
- Response handling. Only a response with the same Call-ID, CSeq and Via branch is accepted; others are ignored. Provisional responses (100 Trying and similar) are recorded, and the final response decides the outcome. Redirects (3xx) are reported, never followed. Responses larger than 64 KB are discarded (UDP) or end the test as malformed (TCP/TLS). The parser understands folded header lines and compact header names.
Limits (SIP_LIMITS on the server):
| Limit | Value |
|---|---|
| Tests per visitor | 20 per hour |
| Tests per verification | 30 per hour |
| Tests per target address | 30 per hour |
| Verifications started per visitor | 10 per hour |
| Verification checks per visitor | 60 per hour |
| Concurrent tests on the server | 4 |
| Pending verification | expires after 72 hours |
| Completed verification | valid for 30 days while the TXT record stays published |
The server stores only SHA-256 hashes of the verification ID and the token, never the values themselves.
How to use the NetTools.tech SIP OPTIONS Diagnostic
Open the SIP OPTIONS Diagnostic. The step bar shows Configure → Verify ownership → Test → Results.
- SIP server (hostname or IP address): for example
sip.example.com. Only the host, nosip:prefix or user. - Port: filled automatically with 5060, or 5061 when you choose TLS, until you edit it yourself.
- Transport: UDP (default), TCP or TLS.
- Advanced (optional): Timeout (2, 4, 6 or 8 s) and SIP domain, which is used in the request URI. For an IP target it defaults to the verified domain.
- Ownership verification. If the target is not covered yet, enter the domain (or a parent domain) and click Start verification. The box shows the record to publish, with a Copy button for each line:
- Name:
_nettools-sip-verification.example.com - Type:
TXT - Value:
nettools-sip-verification=<token>
- Name:
- Publish the record at your DNS provider and click Verify. Once verified, the badge shows the domain and the expiry date; Re-check looks the record up again and Remove verification deletes it on the server and in your browser. Verifications are remembered in this browser until they expire or you remove them.
- Tick I own this SIP infrastructure or have explicit permission to test it. The test does not start without it.
- Click Send SIP OPTIONS. Progress steps show authorization, resolution, sending and analysis; Cancel stops a running test.
- Export the result with CSV, JSON, Copy all or Print. Exports contain no verification ID or token.
Tip
Verify the parent domain (example.com) once to test several SIP hosts below it, such as pbx.example.com and sbc.example.com. Remove the TXT record when you no longer need tests; the authorization ends with it.
Understanding the results
Banner and key figures
| Result | Meaning | What to look for |
|---|---|---|
| SIP Server Responded | A 2xx final response | Green banner with status code and meaning |
| …Authentication Required | 401 or 407: the server wants credentials | A SIP server is responding; NetTools sends none |
| …Request Rejected | 403: refused from this source or for this domain | Often an ACL or a domain/realm the server does not serve |
| …Method Not Allowed | 405: OPTIONS not permitted | The server still answered |
| …Error | Any other final status, including 3xx redirects and 404, 503 | The status code meaning names the reason |
| No SIP Response | Nothing matching arrived within the timeout | Not proof the server is offline or the port closed |
| Connection Refused | TCP refused, or ICMP port unreachable for UDP | Nothing listens on that port and transport |
| Network Unreachable | The network reported no route | Continue with Traceroute |
| TLS Connection Failed | Handshake or certificate validation failed; no SIP request sent | See the TLS certificate card |
| Malformed Response | Something answered, but not with a valid SIP response | Another service on the port, or a truncated reply |
| Verification Required, Rate limited, Destination not allowed, Test not run | The test was refused before anything was sent | The message explains which rule applied |
| KPIs | Target and SIP domain, resolved IP and port, transport with UDP retransmissions, SIP response (with provisional codes), response time with connect and TLS times, server (Server or User-Agent header, or "Not disclosed") | Retransmissions before an answer point at loss or a slow server |
Cards and tables
| Result | Meaning | What to look for |
|---|---|---|
| Authorization | DNS TXT verification of a domain or an administrator-approved target; whether the target was authorized by host name, by DNS link or by the allowlist; verified and valid-until times | Confirms which rule allowed the test |
| TLS certificate (TLS only) | Valid, valid but expiring within 14 days, or not trusted; subject, issuer, validity, host name match, chain trust, TLS version, cipher suite, names in the certificate | Certificate problems are TLS errors, not SIP errors |
| Advertised SIP methods (Allow) | A matrix of 14 common methods, marked advertised or not, plus any others the server lists | Announced only, not tested |
| Advertised extensions (Supported) | Option tags with a short description for known ones, plus Require, Unsupported and Accept | No Supported header means none advertised |
| Response time | Bars for connect, TLS handshake and SIP response, measured from sending the request to the final response | Large connect or handshake times point at the path, not SIP |
| Tests in this session (not stored) | Up to 10 tests with time, target, transport, result and response; Clear session history empties it | Kept in memory only |
| SIP headers | Server, User-Agent, Allow, Supported, Accept, Require, Unsupported, Contact, Via, Record-Route | "Not present" means the server did not send it, often on purpose |
| Raw SIP request and response | Transport, start and finish, provisional responses, UDP retransmissions, notes, the exact request and the final response | Compare Via and Contact for NAT rewriting |
Below the results, buttons open Port Check, Ping, Traceroute, MTR, IP Lookup, the SNMP Diagnostic and, for a hostname, DNS Lookup and DNS Propagation for the same target.
Example: OPTIONS over UDP to a PBX
The values below are illustrative, made up for this guide on documentation addresses; your server's output will differ.
example.com is verified. Target sip.example.com, resolving to 203.0.113.20, UDP port 5060, default timeout 4 s:
SIP Server Responded — 200 OK — the request succeeded.
Target sip.example.com SIP domain sip.example.com
Resolved IP 203.0.113.20 port 5060
Transport UDP
SIP response 200 OK
Response time 38.2 ms
Server ExamplePBX 1.0
Advertised methods INVITE, ACK, CANCEL, BYE, OPTIONS, REGISTER, NOTIFY
Supported extensions replaces, timer, 100relThe raw request starts with OPTIONS sip:sip.example.com SIP/2.0 and carries CSeq: 1 OPTIONS. The methods matrix marks the seven advertised methods; that the server announces INVITE says nothing about whether it would accept a call from you.
The same server tested over TCP on 5060 might return Connection Refused if it only listens on UDP, and a firewall that drops traffic from unknown sources would produce No SIP Response with two UDP retransmissions.
Common use cases
- Commissioning a PBX or SBC: confirm it answers on each transport and port the trunk provider will use.
- After firewall or NAT changes: check that SIP is still reachable, and that the response's Via and Contact headers look as expected.
- Certificate renewal on 5061: verify the new certificate's chain, names and expiry from outside.
- Hardening review: see whether the server discloses its software version in Server or User-Agent and whether it answers unknown sources at all.
- Comparing with your monitoring: reproduce the OPTIONS keepalive that a provider or monitoring system sends.
Troubleshooting
"No SIP Response"
Nothing matching our transaction arrived within the timeout. Common causes: an ACL or fail2ban-style filter that ignores unknown sources, a firewall dropping the port, the server listening on another transport or port, or a SIP ALG on a router mangling the packets. Try TCP and TLS, try a longer timeout, and use Port Check for TCP ports or Ping to confirm the host is up. Do not conclude that the server is offline.
"Connection Refused"
For TCP and TLS, the host refused the connection; for UDP, it returned ICMP port unreachable. Nothing listens on that port with that transport. Check the listener configuration (for example whether TCP or TLS transports are enabled) and the port.
"TLS Connection Failed"
Look at the certificate card. "Host name mismatch" means the certificate does not cover the name you tested; for an IP target, the name checked is the SIP domain. A chain marked "Not trusted" usually means a self-signed certificate or a missing intermediate; for an expired certificate, compare the validity dates on the card. Fix the certificate; the tool will not send SIP over an unauthenticated connection. The SSL Certificate Checker helps with HTTPS certificates on the same host.
403 Forbidden or 404 Not Found
The server answered but refuses requests from the NetTools server or does not serve the domain in the request URI. Set SIP domain under Advanced to the domain your server actually serves, or add the NetTools server to the ACL temporarily.
"Verification Required" or "not authorized"
The TXT record is missing, the verification is still pending or expired, the host is outside the verified domain, or the IP address is not one of the domain's A/AAAA or SIP SRV targets. Re-check the record with DNS Lookup, or check whether it has reached all resolvers with DNS Propagation.
"Destination not allowed" or the IPv6 message
The target resolves to a private, loopback, link-local or otherwise blocked address, or only to IPv6. Test a public IPv4 address of the server, or ask an administrator to approve a private target.
Common mistakes
- Reading silence as "down". Many SIP servers drop OPTIONS from unknown sources by design.
- Treating 401 or 403 as a failure. They prove a SIP server is responding.
- Entering a SIP URI. Enter
sip.example.com, notsip:[email protected]; users and parameters are refused. - Testing UDP only. A server can work over UDP and fail over TCP or TLS, or the other way round.
- Using TLS on 5060. Most servers expect TLS on 5061; the port follows the transport unless you change it.
- Assuming advertised methods work. Allow and Supported are announcements, not test results.
- Leaving the TXT record and ACL changes in place. Remove them when testing is done.
Limitations
- OPTIONS only: no INVITE, REGISTER, SUBSCRIBE or MESSAGE, no authentication, no call setup, no media (RTP) test and no user or extension enumeration.
- One transaction per test: no port ranges, no target lists.
- Silence is ambiguous: without a response the tool cannot tell a filter from a stopped service.
- Advertised methods and extensions are not tested; they may be unavailable or require authentication.
- Redirects are not followed; the 3xx response is shown as received.
- One vantage point: the NetTools server in Latvia; ACLs, geo-blocking and routing may treat your provider differently.
- IPv4 only for now; private networks only through the administrator allowlist.
- Server identification is self-reported and can be hidden or changed by the operator.
Security & privacy
The tool needs no credentials and you should never enter any: the target field refuses users and passwords. Verification works with two random values. The token goes into your public TXT record. The verification ID is kept in your browser's local storage and sent with each test; the server stores only SHA-256 hashes of both, plus the domain, timestamps and your truncated IP address for rate limiting. The page URL contains no IDs or tokens, and exports omit them. Treat the verification ID like a password for testing your domain, and use Remove verification on shared computers.
For each test the server writes an audit entry with the target, resolved IP, port, transport, verified domain and your truncated address. The SIP request identifies itself as the NetTools.tech diagnostic, so it is recognizable in your server logs. Removing the TXT record withdraws the authorization on the next test. See the privacy policy.
Related tools
- Port Check – test whether a TCP port such as 5060 or 5061 accepts connections; guide.
- Ping – check that the host answers ICMP; guide.
- Traceroute – find where the path to an unreachable server ends; guide.
- DNS Lookup – check the TXT record, A records and SIP SRV records; guide.
- SSL Certificate Checker – certificate details for HTTPS services; guide.
- SNMP Diagnostic – read-only SNMP checks of devices you manage; guide.
- Network diagnostics overview.
Summary
The SIP OPTIONS Diagnostic sends a single SIP OPTIONS transaction over UDP, TCP or TLS from the NetTools server to a SIP server whose domain you have verified with a DNS TXT record, or to an administrator-approved address. It reports the status code and what it means, timing, the advertised methods and extensions, all relevant headers and, for TLS, the certificate, which must validate before anything is sent. Any SIP response proves a server is answering; no response proves nothing either way.
Frequently asked questions
What is a SIP OPTIONS request?
OPTIONS is a SIP method defined in RFC 3261 that asks a server or endpoint about its capabilities without setting up a call. The answer carries a status code and usually headers such as Allow and Supported, which is why OPTIONS is widely used as a health check between PBXs, proxies and SIP trunks.
Why do I have to verify my domain before testing?
Sending SIP requests to servers you do not control looks like reconnaissance and can trigger security systems. You publish a DNS TXT record at _nettools-sip-verification.<domain>, and the NetTools server looks that record up again before every test, so removing it ends the authorization.
Does a 401, 403 or 405 response mean the test failed?
No. Any SIP response proves that a SIP server answered: 401 or 407 means it wants authentication, 403 that it refuses the request from this source, 405 that it does not permit OPTIONS. NetTools never sends credentials, so these are expected answers for many locked-down servers.
Why did I get "No SIP Response"?
Many SIP servers, session border controllers and firewalls silently drop OPTIONS from unknown sources to stay invisible to scanners. No response within the timeout therefore does not prove that the server is offline or the port is closed; check source-address filters and the transport first.
Can I test an IP address instead of a hostname?
Yes, if your verified domain's DNS points to it: its A/AAAA records or the targets of its _sip._udp, _sip._tcp or _sips._tcp SRV records. Otherwise only an address an administrator added to the approved targets can be tested; owning a domain does not authorize arbitrary IP addresses.
Does a 200 OK mean calls will work?
No. It shows that the server answered OPTIONS. Calls also depend on registration, authentication, routing, codecs and the RTP media path, none of which this read-only test touches.
Why was no SIP request sent over TLS?
The certificate chain and the host name are validated before anything is sent. If either check fails, the result is reported as a TLS error with the certificate details, and the connection is closed without a SIP request.
Does the tool try INVITE, REGISTER or extension enumeration?
No. The only SIP method in the client is OPTIONS, sent once per test as a single transaction. There is no INVITE, REGISTER, SUBSCRIBE or MESSAGE, no authentication and no user or extension probing, and redirects are reported but never followed.