Free DNS tool
DNS SRV Record Lookup
Find the host, port, priority and weight behind a service from a _service._proto name, like SIP, XMPP or autodiscovery.
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Free DNS tool
Find the host, port, priority and weight behind a service from a _service._proto name, like SIP, XMPP or autodiscovery.
Try , ,
Lookups run in your browser over Google public DNS-over-HTTPS (Cloudflare as fallback). Nothing you enter is sent to Pulsetic.
DNS decides where your domain and email actually go. Pulsetic watches your domain and SSL certificate around the clock.
An SRV (service) record points a specific service to the host and port that provides it. Unlike an A or MX record, an SRV name is structured as _service._protocol.domain, for example _sip._tcp.example.com. The record returns four values: priority, weight, port and target host.
SRV records let a client discover where a service lives without hard-coding a host name, which is why they are used by SIP, XMPP, LDAP, Minecraft and mail autodiscovery. Lower priority is tried first, and weight balances load between targets that share a priority.
A value like "5 0 993 imap.gmail.com" means priority 5, weight 0, port 993, target imap.gmail.com. A client tries the lowest priority first and uses weight to choose between targets that share one.
Because the name is service-specific, you must query the full _service._proto.domain form. Looking up the bare domain returns nothing, which is normal and not a fault.
An SRV name has three parts joined by dots: an underscore service, an underscore protocol, and the domain, as in _sip._tcp.example.com. The service names the application (sip, imaps, xmpp-server) and the protocol is almost always _tcp or _udp. Get either label wrong and the lookup returns nothing, because SRV records exist only at the exact name.
The value holds four fields and a host: priority, weight, port and target. Priority works like MX, lowest first. Weight only matters between records that share a priority, splitting traffic in proportion, so 70 and 30 send roughly seven connections in ten to the first. The port is where the service listens, and the target must resolve to an A or AAAA record, never a CNAME.
Prefer the command line? These return the same records this tool shows:
dig _imaps._tcp.gmail.com SRV +short
nslookup -type=SRV _imaps._tcp.gmail.com
What each record does. Each one has a dedicated lookup in the tabs above.
| Record | What it does | Example value |
|---|---|---|
| A | Maps a domain to an IPv4 address. | example.com → 93.184.216.34 |
| AAAA | Maps a domain to an IPv6 address. | example.com → 2606:2800:220:1:: |
| CNAME | Points one name at another name, as an alias. | www → example.com |
| MX | Names the mail servers that accept email for the domain, each with a priority. | 10 mail.example.com |
| TXT | Holds free-form text, used for SPF, DKIM, DMARC and domain verification. | v=spf1 include:_spf.google.com ~all |
| NS | Lists the authoritative name servers for the domain. | ns1.example.com |
| SOA | Start of authority: the primary name server and the zone refresh, retry and expiry timers. | ns1.example.com . 2026010101 |
| PTR | Reverse record: maps an IP address back to a host name. | 34.216.184.93.in-addr.arpa |
| SRV | Locates the host and port for a specific service. | _sip._tcp → 5060 sip.example.com |
| CAA | States which certificate authorities may issue SSL certificates for the domain. | 0 issue "letsencrypt.org" |
An SRV record tells clients which host and port provide a particular service for a domain. It is queried by a structured name, _service._protocol.domain, and returns a priority, weight, port and target host.
It is _service._protocol.domain, for example _sip._tcp.example.com or _imaps._tcp.gmail.com. Both the service and protocol labels start with an underscore, which is why a plain domain lookup returns no SRV records.
In order: priority (lower is tried first), weight (load balancing between equal priorities), port (where the service listens) and target (the host name to connect to).
Most likely you queried a bare domain. SRV records only exist at a _service._proto name, so enter the full form such as _submission._tcp.example.com. If that still returns nothing, the service simply does not publish an SRV record.
2-minute setup · Cancel any time
No credit card needed
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026