SRV Record Lookup
An SRV record advertises the host and port for a specific service, such as VoIP or chat. Look up any SRV record across 21 global servers to read its priority, weight, port, and target.
SRV needs the full service prefix, not just the domain. Use the format _service._protocol.yourdomain.com.
Examples: _sip._tcp for VoIP, _xmpp-server._tcp for XMPP, _autodiscover._tcp for Exchange or Outlook.
Global DNS Propagation
 New York, USA Google | --- |
| Chicago, USA Gcore | --- |
| Los Angeles, USA Cloudflare | --- |
 Toronto, Canada CIRA | --- |
 Mexico City, MX OpenDNS | --- |
 London, UK Quad9 | --- |
 Frankfurt, Germany DNS.Watch | --- |
 Paris, France FDN | --- |
 Amsterdam, NL OpenNIC | --- |
 Moscow, Russia Yandex | --- |
 Singapore Singtel | --- |
 Tokyo, Japan IIJ | --- |
 Mumbai, India Google India | --- |
 Seoul, Korea KT | --- |
 Dubai, UAE Etisalat | --- |
 Sydney, Australia Telstra | --- |
 Auckland, NZ Cloudflare | --- |
 São Paulo, Brazil NIC.br | --- |
 Buenos Aires, AR Telecom Arg | --- |
 Johannesburg, ZA ISPA | --- |
 Cairo, Egypt Telecom Egypt | --- |
DNS Map
About SRV records
An SRV (Service) record tells clients where to reach a named service and on which port. Instead of hardcoding a hostname and port, an application looks up the SRV record and connects to whatever it points to. This lets you move a service or change its port without reconfiguring clients. For the full explanation, read what is an SRV record.
The record name encodes the service and protocol, for example _sip._tcp.example.com. Each value has four fields: priority, weight, port, and target host. Priority works like MX, where lower is tried first. Weight splits traffic between records of equal priority. The port and target say exactly where to connect.
Each row shows one of the 21 global servers and the SRV values it returned, printed as priority, weight, port, then target, for example 10 60 5060 sipserver.example.com. Every server should return the same values once propagated. A row with no value usually means you entered the domain without the _service._protocol prefix, so double-check the name format above.