Free SRV Record Lookup.
Look up SRV records for any domain in seconds. Verify service routing (priority, weight, port, target), confirm TTL values, and troubleshoot misconfigurations fast.
SRV Record Lookup.
How does SRV Record Lookup work?
Enter a domain name (e.g., gmail.com) or a full SRV record name (e.g., _imaps._tcp.gmail.com) and click "Check". Our tool queries DNS for SRV records and returns the service endpoints it finds—along with TTL (time-to-live)—so you can validate changes and troubleshoot caching.
What is an SRV record?
An SRV record (Service record) tells clients where to find a specific service for a domain. It can define the target hostname and port, plus routing rules like priority and weight—often used for VoIP, messaging, and some SaaS integrations.
When should you check an SRV record?
- When a service connection fails (VoIP, chat, directory, etc.)
- After changing service providers or endpoints
- When verifying routing rules (priority/weight) for redundancy
- When troubleshooting DNS propagation and caching
What do SRV fields mean?
Priority: Which target is preferred (lower = preferred)
Weight: Load balancing between targets with the same priority
Port: The service port clients should use
Target: The hostname providing the service
Get 50 monitors with 5-minute checks totally FREE.
Try UpTimeRobot - the world's leading website monitoring service!
Start monitoring for freeFrequently asked questions.
What SRV name should I look up (the “_service._proto” format)?
SRV records live on a specific hostname like
_service._proto.domain.com(for example,_ldap._tcp.example.com). If you only lookup example.com, you may see nothing even when SRV is configured.What does an SRV record contain?
An SRV record tells clients which host and port to use for a service, plus routing rules like priority and weight.
How do “priority” and “weight” affect which server is used?
Clients typically try the lowest priority first. If multiple records share the same priority, weight is used to distribute traffic among them.
Does the SRV “target” need an A/AAAA record?
Yes. The SRV target should resolve to an IP via an A or AAAA record so clients can connect to it.
Can an SRV record point to a CNAME?
It’s not considered a valid setup by the SRV spec—SRV targets are expected to have A/AAAA records rather than being aliases.
What are SRV records commonly used for?
SRV is widely used for service discovery in protocols like SIP, XMPP, and LDAP, where clients need the right host and port for the service.
My SRV record exists—why isn’t the service working?
Common causes: you queried the wrong _service._proto name, the target hostname doesn’t resolve (missing A/AAAA), the port is wrong, or clients don’t support SRV for that specific service.
Get your FREE account now, 50 monitors included!
Try UpTimeRobot - the world’s leading website monitoring service!
Start monitoring for free
Incident management
Status pages
MCP
Integrations