Requests Over Time
Data Served Over Time
Client HTTP Version Used
Requests Volume by Country
Frequently Accessed Paths
Note: Frequently Accessed Paths metric uses Cloudflare's adaptive aggregation system which may show higher request counts than the Requests Volume by Country metric due to different data collection methods. Both metrics are accurate for their respective aggregation approaches.
Top Users
Note on IP addresses and security: IP addresses shown here are not treated as private identifiers by v.recipes; they are a fundamental part of how networks communicate and are necessary for operating DNS services. If you run public-facing services, please be aware that security and reliability of those services (for example protecting against DDoS or brute-force attacks) are the responsibility of the operator. Public services are inherently exposed to risks such as distributed denial-of-service (DDoS) attacks and credential guessing; operators should anticipate these possibilities and employ appropriate network and host-level protections.
v.recipes is responsible for maintaining the security and reliability of our own services (including DNS infrastructure). We do not manipulate users' DNS queries or responses from upstream DNS providers. If you experience network-level incidents such as sustained DDoS activity, please work with your ISP and network administrators to identify and apply appropriate mitigations. Our DNS system is designed to avoid generating excessive queries to other networks, and cannot be used to direct attacks at external DNS providers.
Your Estimated Usage
Privacy Notice: The data displayed below represents DNS requests associated with your current IP address and is calculated based on your last 1000 DNS requests. Please note that this information may be inaccurate if you are using shared network infrastructure such as public VPN services, corporate proxies, or shared internet connections. Our DNS service operates as a relay between users and upstream DNS providers (Cloudflare, Google, etc.), which means we cannot directly monitor individual user activity. We collect and analyze connection metadata solely for operational purposes including rate limiting, DDoS protection, and service optimization to ensure reliable DNS service for all users. For more details about our data practices, please refer to our Privacy Policy and Technical Details pages.