What is an SRV record?

An SRV (Service) record tells clients which host and port provide a specific service for a domain, such as SIP, XMPP, LDAP, or Minecraft. Each record carries a priority, weight, port, and target hostname under a name like _service._proto.example.com.

How do I use this tool?

Enter the full SRV name including the service and protocol labels (for example _sip._tcp.example.com) and run the lookup. The tool queries the SRV record server-side and lists each entry's priority, weight, port, and target host.

Why do SRV records matter?

They let a service move to a different server or port without users having to change any settings, since clients discover the location from DNS. They also enable load balancing and failover across multiple target hosts.

How do I read the priority and weight values?

Clients contact the target with the lowest priority number first, and if several targets share the same priority, weight distributes traffic proportionally among them. The port field tells the client which port to connect to on the chosen target.

Why does my lookup return no SRV record?

SRV records only exist for the exact _service._proto name you query, so a bare domain like example.com will not resolve. Double-check the service and protocol labels and the underscore prefixes, since a typo there returns an empty result.

SRV Record Look Up

Related tools

Domain name

What do you want to look up?

Blacklist Look Up

Looks up whether this domain's IP address (or the IP address you entered) appears on common email blacklists (DNSBL) — being listed can cause outgoing mail to be rejected or sent to spam.

Also look up blacklist status when I run this search

What this is

SRV records advertise the host and port for a specific service and protocol, using a structured name like _sip._tcp.example.com. Only applications designed to look them up (VoIP, XMPP, some Microsoft services) use them.

How to read your result

Each result names priority, weight, port, and target host. Absence is only a problem if some application specifically requires the record — check that application's documentation for the exact _service._proto name it expects.

Common problems and how to fix them

SRV published under the wrong name

How it shows up: The application ignores the record entirely; autodiscovery keeps failing.

How to fix it: The name must match exactly what the application queries — including the underscores and the protocol label (_tcp vs _udp). Copy the exact name from the vendor's setup guide.

SRV target is a CNAME or lacks an address record

How it shows up: Some clients connect, others fail — strict implementations refuse CNAME targets.

How to fix it: Point the SRV target at a hostname that has its own A/AAAA record.

Frequently asked questions

What is an SRV record?: An SRV (Service) record tells clients which host and port provide a specific service for a domain, such as SIP, XMPP, LDAP, or Minecraft. Each record carries a priority, weight, port, and target hostname under a name like _service._proto.example.com.
How do I use this tool?: Enter the full SRV name including the service and protocol labels (for example _sip._tcp.example.com) and run the lookup. The tool queries the SRV record server-side and lists each entry's priority, weight, port, and target host.
Why do SRV records matter?: They let a service move to a different server or port without users having to change any settings, since clients discover the location from DNS. They also enable load balancing and failover across multiple target hosts.
How do I read the priority and weight values?: Clients contact the target with the lowest priority number first, and if several targets share the same priority, weight distributes traffic proportionally among them. The port field tells the client which port to connect to on the chosen target.
Why does my lookup return no SRV record?: SRV records only exist for the exact _service._proto name you query, so a bare domain like example.com will not resolve. Double-check the service and protocol labels and the underscore prefixes, since a typo there returns an empty result.