Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1325 ms totalFIX
https://share.google/U54px4anxc5wgUpxN
65 ms · HTTP/1.1
https://www.google.com/share.google?q=U5...
98 ms · HTTP/1.1
https://www.brickyard.ae/?shem=aimgspe,
1163 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://share.google/U54px4anxc5wgUpxN | 302 | 65 ms | HTTP/1.1 | sffe |
| 2 | https://www.google.com/share.google?q=U5... | 301 | 98 ms | HTTP/1.1 | gws |
| 3 | https://www.brickyard.ae/?shem=aimgspe, | 200 | 1163 ms | HTTP/1.1 | Vercel |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BReverse DNS0/2 IPs match cert SANREVIEW
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html class="google mmfb" lang="en">
<head>
<script nonce="Eo1REy1ywCCGT2YyKpcXkQ">
(function(H){H.className=H.className.replace(/\bgoogle\b/,'google-js')})(document.documentElement)
</script>
<meta charset="utf-8">
<meta content="initial-scale=1, minimum-scale=1, width=device-width" name="viewport">
<title>
share.google
</title>
<link href="//fonts.googleapis.com/css?family=Open+Sans:300,400,600,700|Product+Sans:400&subset=latin"
rel="stylesheet" nonce="Eo1REy1ywCCGT2YyKpcXkQ">
<link href="//www.google.com/css/maia.css" rel="stylesheet" nonce="Eo1REy1ywCCGT2YyKpcXkQ">
</head>
<body>
<div class="maia-header" id="maia-header">
<div class="maia-aux">
<h1>
<a href="http://www.google.com/"><img alt="Google"
src="//www.google.com/images/branding/googlelogo/1x/googlelogo_color_116x41dp.png"
srcset="//www.google.com/images/branding/googlelogo/2x/googlelogo_color_116x41dp.png 2x"></a>
</h1>
<h2>
share.google
</h2>
</div>
</div>
<div id="maia-main">
<p>
Something went wrong and this URL isn’t available
</p>
</div>
<div id="maia-signature"></div>
<div class="maia-footer" id="maia-footer">
<div id="maia-footer-global">
<div class="maia-aux">
<ul>
<li>
<a href="http://www.google.com/">Google</a>
</li>
<li>
<a href="http://www.google.com/policies/">Privacy & Terms</a>
</li>
</ul>
</div>
</div>
</div>
</body>
</html>
BTLS Certificate Expiry & Recommendations58 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
CCDN & DeliveryActionAssets on Vercel (host www.brickyard.ae, 3 assets); document served directly from origin (Google)REVIEW
Asset hosts on a CDN
- www.brickyard.ae — Vercel · assets: 3 · Cache Status: MISS
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 24 ms lookupPASS
| A | 216.239.32.27 |
| AAAA | 2001:4860:4802:32::1b |
| CNAME | — |
| NS | ns2.googledomains.com, ns1.googledomains.com, ns4.googledomains.com, ns3.googledomains.com |
| MX | — |
| TXT | SPF v=spf1 -all |
| 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
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ACAA Recordsissue: pki.googPASS
A+Multi-Resolver DNS SpeedMean 12ms across 3 resolvers (spread 19ms)PASS
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Trailing Slash
HTTP → HTTPS
Use a permanent redirect (301 or 308) instead of a temporary one
A+Domain Intelligenceshare.google — via MarkMonitor Inc., 1 years, 9 months oldPASS
89 days
January 15, 2027
58 days
Issued by Google Trust Services
1 years, 9 months
Registered January 15, 2025
Not enabled
Protects against DNS spoofing
Unknown
2001:4860:4802:32::1b
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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