Infrastructure Tools
GGX Labs provides a suite of intelligence tools designed to analyze publicly accessible internet infrastructure including domains, DNS, and IP-level routing systems.
Each tool below is built around a single, well-defined signal type — domain records, DNS resolution, IP routing, HTTP headers, or site readiness — rather than trying to be one giant, all-purpose lookup box. That separation matters in practice: a domain investigation question and a DNS delegation question are different problems, and conflating them into a single undifferentiated report usually just buries the answer you actually need under fields you don't. Picking the right tool up front gets you to a usable answer faster.
None of the tools here require you to install anything, authenticate against the target, or access anything beyond what is already publicly exposed on the internet. Every lookup queries public registries, resolvers, and endpoints — the same category of data a registrar, a DNS provider, or a web server already makes available to any client that asks.
Code Engine
Secure launcher for protected GGX Labs resources.
IP Intelligence
Analyze IP addresses, geolocation, ASN, ISP, hosting, and network details.
DNS Analyzer
Inspect DNS records including A, AAAA, MX, TXT, NS, CNAME, and SOA.
Domain Intelligence
Investigate domains, infrastructure, hosting, technologies, and security insights.
WHOIS Lookup
Retrieve WHOIS and RDAP records, registrar details, nameservers, and domain expiry.
SSL Checker
Analyze SSL/TLS certificates, HTTPS configuration, certificate chain, and expiry.
Security Headers Analyzer
Audit HTTP security headers including CSP, HSTS, X-Frame-Options, and Permissions Policy.
HTTP Header Analyzer
Inspect HTTP request and response headers for diagnostics and troubleshooting.
Email Security Analyzer
Verify SPF, DKIM, DMARC, MX records, and email authentication security.
AdSense Approval Rate Checker
Evaluate website readiness and identify issues affecting Google AdSense approval.
Which tool for which job
If you're not sure where to start, the fastest way to pick is to ask what you're actually trying to find out. The table below maps each tool to the situation it's built for and the specific signals it surfaces, so you can go straight to the right lookup instead of working through all of them.
IP Intelligence
Best used when an IP address shows up in a log file, a security alert, or a piece of unfamiliar traffic and you need to understand what's actually behind it before deciding how to respond.
DNS Analyzer
Best used when you need to confirm exactly how a domain resolves right now — whether that's debugging a misconfigured mail record, checking propagation after a migration, or reviewing a domain you don't control.
Domain Intelligence
Best used at the start of a vendor review, a fraud check, or any situation where you need to understand who is actually behind a domain and how long it has existed.
HTTP Header Analyzer
Best used when auditing a site's security posture — checking whether HSTS, CSP, and other protective headers are actually configured, or whether a server is leaking more information than it should in its responses.
AdSense Approval Rate Checker
Best used before submitting a site for AdSense review, to catch the structural and content issues that commonly cause rejections before they cost you a review cycle.
Getting the most out of a lookup
A single query against any of these tools will usually get you a useful answer, but the more valuable habit is to run related lookups together rather than in isolation. A domain's registration details tell you who registered it and when; its DNS records tell you where it currently points; its HTTP headers tell you what kind of server is actually answering requests there. Any one of these on its own is a data point. Together, they're a picture.
For example, a domain registered within the last few days, pointing through DNS to a hosting provider with a poor reputation, serving a page with no meaningful security headers configured, is a very different finding than the same domain having existed for a decade on stable, well-known infrastructure. None of those three facts alone would tell you that — it's the combination that's meaningful.
It's also worth treating a single lookup as a snapshot rather than a permanent record. DNS records change when a site migrates hosting providers. WHOIS data updates when a domain is renewed or transferred. HTTP headers change with every deployment. If you're tracking something over time — a suspicious domain, a vendor's infrastructure, your own production environment — re-running the same lookup periodically is far more informative than a one-time check.
Who these tools are built for
Security teams
Triage indicators of compromise, review suspicious domains flagged by monitoring systems, and confirm hosting and routing context around an incident without switching between five different registries and lookup sites.
Developers & SREs
Debug DNS propagation during a migration, confirm security headers are actually being served in production, and verify domain and hosting configuration matches what was intended after a deploy.
Site owners & publishers
Check a site's readiness before an AdSense submission, confirm domain and hosting details are configured correctly, and get an outside view of what a visitor's browser and a search crawler actually see.
Data sources and scope
Every tool on this page draws from publicly available sources: authoritative DNS resolvers, public WHOIS and registrar records, regional internet registry (RIR) allocation data, and standard HTTP responses returned by the server you're querying. None of these require credentials, none bypass access controls, and none involve scanning ports or probing a system beyond a normal request a browser or resolver would make on its own.
That scope is intentional. These tools are built for visibility and analysis of information that is already exposed by design — not for penetration testing, exploitation, or anything that requires authorization from a system's owner. If your work requires that kind of testing, it needs to happen through a properly scoped engagement with explicit permission, separate from anything offered here.
Because much of this data comes from third-party registries and resolvers, freshness varies by source. DNS and HTTP header lookups reflect the live state of a target at query time. WHOIS data reflects whatever the registrar's public record currently shows, which can lag a few hours or days behind an actual ownership change. Treat every report as a snapshot of the public record at the moment you ran the query, not a permanently accurate ledger.
Frequently asked questions
Do I need an account to use these tools?
Standard lookups across Domain Intelligence, DNS Analyzer, IP Intelligence, HTTP Header Analyzer, and the AdSense Approval Rate Checker are available without a mandatory account for casual use. Higher-volume usage, saved reports, and API access typically require signing in.
Can these tools scan or test a system for vulnerabilities?
No. Every tool here is scoped to publicly exposed information — DNS records, WHOIS data, routing announcements, and standard HTTP responses. None of them perform port scanning, exploitation, or credential testing, and none are a substitute for an authorized security assessment.
Why do IP Intelligence and Domain Intelligence sometimes disagree on hosting?
Domain Intelligence looks at registrar and registration data, while IP Intelligence looks at where the current DNS resolution actually points. A domain can be registered through one company while being hosted, via DNS, on entirely different infrastructure — this is normal and often expected, especially behind CDNs.
How accurate is the geolocation shown in IP Intelligence?
It's generally reliable at the country level and often accurate to the city for fixed infrastructure, but it's an estimate drawn from public geolocation datasets and RIR allocation records — not a precise physical address. Mobile networks, VPN exit nodes, and reassigned IP space can all reduce accuracy.
What does the AdSense Approval Rate Checker actually check?
It reviews structural and content signals commonly associated with AdSense approval outcomes — things like content depth, site structure, and policy risk flags — so you can address likely issues before submitting for review rather than finding out after a rejection.
What is Code Engine, and why isn't it listed with the other tools?
Code Engine is a secured launcher for internal GGX resources, gated behind authentication. It isn't a public analysis tool in the same sense as the others, so it's intentionally kept out of the comparison table above.
Is there an API for these tools?
Programmatic access is available for teams that want to fold domain, DNS, IP, or header intelligence into their own dashboards or workflows. API usage is generally tied to an account and subject to its own rate limits, separate from the interactive tools on this page.