Yes, subdomain discovery using DNS queries is completely legal. DNS is a public service, and querying it for information is no different than looking up a phone number in a directory. However, what you do after discovering subdomains may have legal implications. Only test security on domains you own or have explicit permission to test. Unauthorized penetration testing is illegal.
DNS brute force is highly accurate for finding subdomains that have DNS records, but it only finds what you specifically look for. Our tool checks 90+ common subdomain names, which catches the most frequently used ones. However, uncommon or custom subdomains (like project123.example.com) won't be found unless they're in our wordlist. Advanced enumeration tools use dictionaries with millions of names for more comprehensive discovery.
Just because a subdomain exists in DNS doesn't mean it's publicly accessible. Many subdomains have IP restrictions (only accessible from corporate networks), require authentication (login pages), or are behind firewalls. Finding a subdomain only tells you it exists; it doesn't grant access. Attempting to bypass authentication or access restrictions is illegal without permission.
No single method finds all subdomains. DNS brute force finds subdomains by guessing names. Other methods include certificate transparency logs (SSL certificates list subdomains), search engines (Google dorking), web archives, and reverse DNS. A comprehensive subdomain enumeration combines multiple techniques. Large organizations can have thousands of subdomains that aren't in common wordlists.
If you find a vulnerability on your own domain, fix it immediately and investigate how it was created. If you discover a vulnerability on someone else's domain during research, follow responsible disclosure practices: notify the organization privately, give them reasonable time to fix it (typically 90 days), and don't publicly disclose details until it's patched. Many companies have bug bounty programs that reward security researchers.
Some domains use wildcard DNS records (*.example.com) that resolve any subdomain to the same IP address. This makes subdomain enumeration difficult because every query returns a positive result, even for non-existent subdomains. Advanced tools detect wildcard configurations and filter results, but it complicates identifying legitimate vs. catch-all subdomains.
For security purposes, scan quarterly or whenever major infrastructure changes occur. Set up automated monitoring to alert you when new subdomains are created, as unauthorized subdomains can indicate a security breach. For competitive intelligence, monthly scans provide insights into competitors' new services or products. Use continuous monitoring for high-security environments.
A records point to IPv4 addresses (like 192.168.1.1), while AAAA records point to IPv6 addresses (like 2001:0db8:85a3::8a2e:0370:7334). Modern websites often have both for compatibility. IPv4 is still dominant, but IPv6 adoption is growing. Our tool checks both types to ensure comprehensive discovery of all configured subdomains.
Yes, deleted subdomains can linger in DNS caches (based on TTL settings), certificate transparency logs (permanent record), search engine caches, web archives (Wayback Machine), and third-party databases. Even after removing a subdomain from your DNS, it may be discoverable through historical records for months or years. Plan subdomain naming carefully.