Answers about website, DNS, SSL, and network diagnostics
Gitae FAQ
Frequently asked questions about Gitae, website availability checks, DNS lookup, SSL and TLS certificates, port checks, ping, traceroute, domain data, IP lookup, and public diagnostics. Use this page to understand what each tool checks, how to interpret warnings, why results can differ between Russia and Finland, and what Gitae can or cannot prove.
What this FAQ helps you answer
This FAQ is the main reference page for short, searchable answers about Gitae, its diagnostics tools, and common troubleshooting questions. It covers website checks, DNS records, SSL and TLS errors, ports, ping, traceroute, redirects, hosting clues, domain data, and public network reachability.
The goal is to help visitors move from a vague symptom like “my site is down” or “SSL looks broken” to the right next tool and a more credible technical explanation.
How Gitae should be interpreted
Gitae is designed for honest public diagnostics. It shows what a server-side check can actually observe instead of pretending to prove how every country, provider, or device sees the same target.
That matters for SEO and trust: concise answers are useful only when they stay precise about limits, uncertainty, and what the evidence can really support.
Why comparison by location matters
Some failures only appear from specific routes, resolvers, or filtering environments. That is why location-sensitive checks compare Russia and Finland in one report when a comparison adds real signal.
For tools where a second location would not materially improve the answer, Gitae stays intentionally single-result to avoid fake complexity.
How this page supports the rest of the site
This page should answer the short version of high-intent questions, while deeper workflows belong in guides and tool pages. That structure improves usability and creates stronger internal linking between FAQs, tools, and educational content.
As the product grows, keep adding questions that reflect real search phrasing, real support conversations, and real result interpretation problems.
Frequently asked questions about Gitae and website diagnostics
What is Gitae?
Gitae is a public diagnostics toolkit for websites, domains, IP addresses, DNS, TLS and SSL, ports, routing, and related infrastructure checks.
Is Gitae free to use?
Yes. Gitae is built as a free public diagnostics toolkit for public targets and common troubleshooting workflows.
Do I need an account to run a check?
No. Core public diagnostics are designed to be usable without creating an account.
What can I check with Gitae?
You can check website availability, DNS records, SSL certificates, open ports, ping, traceroute, hosting hints, CMS signals, domain data, reverse DNS, and IP-related ownership context.
How is Gitae different from a basic website down checker?
A basic uptime checker often stops at a yes-or-no answer. Gitae goes further by showing timings, redirect behavior, DNS answers, TLS details, response headers, reachability, and location-specific differences when they matter.
Where do Gitae checks run from?
Location-sensitive diagnostics run from Russia and Finland and return one combined report. This helps reveal differences caused by routing, DNS resolution, TLS presentation, CDN edge selection, or filtering policy.
Why can a website work in one country but fail in another?
A site can behave differently by country because of DNS differences, routing issues, CDN edge selection, TLS presentation, firewall policy, provider filtering, or server-side geo rules. A two-location check helps surface that kind of mismatch.
Does Gitae use browser-side guesses for network data?
No. Gitae focuses on server-side diagnostics, which means DNS, TCP, TLS, ping, traceroute, and related measurements come from the backend instead of browser APIs.
What does Website Checker show?
Website Checker shows the normalized target, redirect chain, final URL, HTTP status, resolved IP addresses, response headers, and timing data such as DNS resolution time, TCP connect time, TLS handshake time, TTFB, and overall response time.
What does TTFB mean in a website check?
TTFB means time to first byte. In practice, it helps show how long it took before the server started sending the response after connection setup and any TLS negotiation.
If I see HTTP 403 or 503, is the website down?
Not necessarily. A 403 or 503 still means the request reached a server and received an HTTP response. That is different from a DNS failure, timeout, TLS error, or refused TCP connection.
Can redirects hide a real website problem?
Yes. Redirects can hide loops, slow final hops, protocol mismatches, broken destination pages, or country-specific behavior. That is why redirect chains should be read before assuming the site is healthy.
When should I use DNS Lookup instead of Website Checker?
Use DNS Lookup when the question is about records such as A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, or PTR. Use Website Checker when you want to see the full request path and final HTTP behavior.
What is the difference between DNS Lookup, nslookup, and dig on Gitae?
They overlap, but the presentation differs. DNS Lookup is the most general structured view, while nslookup and dig keep a more command-oriented style and raw output that many technical users still prefer.
When should I use SSL Checker?
Use SSL Checker when you need certificate-specific details such as issuer, subject, SAN names, expiration, hostname matching, chain summary, and visible TLS protocol support.
What does Port Checker prove?
Port Checker shows whether a public TCP port appears open, refused, timed out, or otherwise unreachable from the probe locations. It is useful when a service seems online at the DNS level but not reachable over the expected port.
Can Gitae replace full monitoring or observability?
No. Gitae is strongest as a focused first-response diagnostics layer. It does not replace full observability, synthetic fleets, RUM, logging, metrics, or incident response systems.
Is Gitae self-hostable?
Yes. Gitae is positioned as a self-hostable diagnostics toolkit and favors straightforward server-side checks over unnecessary black-box complexity.
Can I test localhost, private IP ranges, or internal hostnames?
No. Public tools are designed for safer public diagnostics, so localhost, private ranges, and internal hostnames are blocked.
Who is Gitae for?
Gitae is useful for founders, freelancers, operators, support engineers, developers, and anyone who needs a faster path from a website problem to a technically credible next step.