Infrastructure
· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS1 PTR record(s) found (no cert data to match against)REVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 34 ms lookupPASS
| A | 139.59.88.37 |
| AAAA | — |
| CNAME | — |
| NS | ns09.domaincontrol.com, ns10.domaincontrol.com |
| MX | — |
| TXT | google-site-verification=ZNENIH_-reMxYwowCWRR7vRB58ge4qlY4NUhknZjkfI |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 38ms across 3 resolvers (spread 13ms)PASS
ARedirect Chain1 redirect(s), 811 ms totalPASS
http://gst-recon.com
311 ms · HTTP/1.1
https://gst-recon.com/
500 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | http://gst-recon.com | 301 | 311 ms | HTTP/1.1 | nginx/1.24.0 (Ubuntu) |
| 2 | https://gst-recon.com/ | 200 | 500 ms | HTTP/1.1 | nginx/1.24.0 (Ubuntu) |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 33 URLsPASS
# robots.txt for gst-recon.com
# Allow all crawlers
User-agent: *
Allow: /
# Disallow signed-in, admin and private pages. /download-report/<key> links are a user's own
# report (sent by email): never to be indexed.
Disallow: /app/
Disallow: /login
Disallow: /logout
Disallow: /admin-panel
Disallow: /download-report/
Disallow: /un-authorised
# Allow blog pages (important for SEO)
Allow: /blog
Allow: /blog/
# Allow public pages
Allow: /privacy-policy
Allow: /tnc
# Sitemap location
Sitemap: https://gst-recon.com/sitemap.xml
# Crawl-delay for bots (optional, prevents overload)
Crawl-delay: 1
# Specific rules for major search engines. A crawler with its own group ignores the * group,
# so each repeats the full private list.
User-agent: Googlebot
Allow: /
Disallow: /app/
Disallow: /login
Disallow: /logout
Disallow: /admin-panel
Disallow: /download-report/
Disallow: /un-authorised
User-agent: Bingbot
Allow: /
Disallow: /app/
Disallow: /login
Disallow: /logout
Disallow: /admin-panel
Disallow: /download-report/
Disallow: /un-authorised
# Block bad bots (optional)
User-agent: MJ12bot
User-agent: AhrefsBot
Disallow: /
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
A+Domain Intelligencegst-recon.com — via GoDaddy.com, LLC, 6 years, 9 months old, hosted on DigitalOceanPASS
103 days
February 19, 2027
No certificate data
6 years, 9 months
Registered February 19, 2020
Not enabled
Protects against DNS spoofing
DigitalOcean
ASN AS14061
139.59.88.37
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice