tools.ggxlabs.in — 12 tools, public, read-only
Infrastructure Tools
A suite of intelligence tools for analyzing publicly accessible internet infrastructure — domains, DNS, and IP-level routing — built as separate, single-purpose lookups rather than one all-purpose report.
Each tool below is built around one signal type. A domain investigation and a DNS delegation check are different problems, and conflating them into a single undifferentiated report tends to bury the answer you actually need under fields you don't. Picking the right tool up front gets you to a usable answer faster — and every lookup queries data that's already publicly exposed, with nothing to install or authenticate against the target.
Code Engine
Secure launcher for protected GGX Labs resources.
A secured, authenticated launcher for internal GGX resources — not a public analysis tool, and not something most visitors will need to open directly.
IP Intelligence
Analyze IP addresses, geolocation, ASN, ISP, hosting, and network details.
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
Inspect DNS records including A, AAAA, MX, TXT, NS, CNAME, and SOA.
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
Investigate domains, infrastructure, hosting, technologies, and security insights.
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.
WHOIS Lookup
Retrieve WHOIS and RDAP records, registrar details, nameservers, and domain expiry.
$ run whois_lookupASN Lookup
Identify autonomous systems, network holders, CIDR allocations, registry, country, and abuse contacts.
Best used when you have an IP address and need to identify the autonomous system, network holder, CIDR allocation, registry, country, and abuse contact tied to that address.
Subdomain Finder
Discover passive subdomains, resolve hosts, check alive endpoints, and map domain attack surface.
Best used when mapping a domain's publicly discoverable attack surface and identifying subdomains, resolved IPs, and hosts that are currently reachable.
SSL Checker
Analyze SSL/TLS certificates, HTTPS configuration, certificate chain, and expiry.
$ run ssl_checkerSecurity Headers Analyzer
Audit HTTP security headers including CSP, HSTS, X-Frame-Options, and Permissions Policy.
$ run security_headers_analyzerHTTP Header Analyzer
Inspect HTTP request and response headers for diagnostics and troubleshooting.
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.
Email Security Analyzer
Verify SPF, DKIM, DMARC, MX records, and email authentication security.
$ run email_security_analyzerAdSense Approval Rate Checker
Evaluate website readiness and identify issues affecting Google AdSense approval.
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 will usually get you a useful answer, but the more valuable habit is running related lookups together. A domain's registration tells you who registered it and when; its DNS tells you where it points; its headers tell you what's actually answering requests. Any one is a data point — together they're a picture.
A domain registered days ago, pointing through DNS to a poorly-reputed host, serving a page with no security headers configured, is a very different finding than the same domain on stable infrastructure for a decade. None of those three facts alone tells you that — the combination does.
Treat a lookup as a snapshot, not a permanent record. DNS changes on migration, WHOIS updates on renewal or transfer, headers change with every deploy. If you're tracking something over time, re-running the same lookup periodically beats a one-time check.
Who these tools are built for
Security teams
Triage indicators of compromise, review suspicious domains flagged by monitoring, and confirm hosting and routing context around an incident without five tabs of registries.
Developers & SREs
Debug DNS propagation during a migration, confirm security headers are actually served in production, and verify config matches intent after a deploy.
Site owners & publishers
Check readiness before an AdSense submission, confirm domain and hosting are configured correctly, and see what a crawler actually sees.
Data sources and scope
Every tool draws from public sources: authoritative DNS resolvers, public WHOIS and registrar records, RIR allocation data, and standard HTTP responses. Nothing requires credentials, bypasses access controls, or probes a system beyond a normal request a browser or resolver already makes.
That scope is intentional. These tools are for visibility into information already exposed by design — not penetration testing or exploitation. Work that requires that kind of testing needs a properly scoped engagement with explicit authorization, separate from anything offered here.
Freshness varies by source. DNS and header lookups reflect live state at query time; WHOIS reflects the registrar's public record, which can lag an ownership change by hours or days. Treat every report as a snapshot, not a 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 perform port scanning, exploitation, or credential testing, and none 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 current DNS resolution actually points. A domain can be registered through one company while hosted, via DNS, on entirely different infrastructure — normal and often expected behind a CDN.
How accurate is the geolocation shown in IP Intelligence?+
Generally reliable at the country level and often accurate to city for fixed infrastructure, but it's an estimate from public geolocation datasets and RIR records, not a precise physical address. Mobile networks, VPN exits, and reassigned IP space can reduce accuracy.
What does the AdSense Approval Rate Checker actually check?+
Structural and content signals commonly associated with AdSense approval outcomes — content depth, site structure, policy risk flags — so you can address likely issues before submitting rather than finding out after a rejection.
Is there an API for these tools?+
Programmatic access is available for teams folding domain, DNS, IP, or header intelligence into their own dashboards or workflows. API usage is tied to an account and subject to its own rate limits, separate from the interactive tools on this page.