Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations34 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
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 26 ms lookupPASS
| A | 160.153.0.223 |
| AAAA | — |
| CNAME | smartg4.com |
| NS | ns36.domaincontrol.com, ns35.domaincontrol.com |
| MX | — |
| TXT | SPF v=spf1 include:secureserver.net -all google-site-verification=dfJZ7YxCZ_zdaQBQgGKFYCOyqRayqbAgPj9XWR1q6mQ |
| 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 CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 9ms across 3 resolvers (spread 9ms)PASS
ARedirect Chain1 redirect(s), 327 ms totalPASS
https://www.smartg4.com
174 ms · HTTP/1.1
https://smartg4.com/
153 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.smartg4.com | 301 | 174 ms | HTTP/1.1 | cloudflare |
| 2 | https://smartg4.com/ | 200 | 153 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 144 URLsPASS
# robots.txt for smartg4.com
# Last updated: 2026-09-21 — full AI + global search engine coverage
# ── Standard search engines ──────────────────────────────────────────────────
User-agent: Googlebot
Allow: /
User-agent: Bingbot
Allow: /
User-agent: Slurp
Allow: /
User-agent: DuckDuckBot
Allow: /
# AI crawlers — ChatGPT / OpenAI
User-agent: GPTBot
Allow: /
User-agent: ChatGPT-User
Allow: /
# AI crawlers — Claude / Anthropic
User-agent: ClaudeBot
Allow: /
User-agent: anthropic-ai
Allow: /
User-agent: Claude-Web
Allow: /
# AI crawlers — Perplexity
User-agent: PerplexityBot
Allow: /
# AI crawlers — Google Gemini
User-agent: Google-Extended
Allow: /
User-agent: Gemini
Allow: /
# AI crawlers — Meta AI
User-agent: meta-externalagent
Allow: /
User-agent: FacebookBot
Allow: /
# AI crawlers — Cohere
User-agent: cohere-ai
Allow: /
# AI crawlers — DeepSeek
User-agent: DeepSeekBot
Allow: /
# AI crawlers — ByteDance / TikTok AI
User-agent: Bytespider
Allow: /
# AI crawlers — Apple Intelligence
User-agent: Applebot-Extended
Allow: /
User-agent: Applebot
Allow: /
# AI crawlers — Baidu AI
User-agent: Baiduspider
Allow: /
# AI crawlers — Yandex AI (Alice)
User-agent: YandexBot
Allow: /
# AI crawlers — xAI / Grok
User-agent: Grok
Allow: /
# AI crawlers — Mistral AI
User-agent: MistralBot
Allow: /
# AI crawlers — Amazon Alexa / Amazonbot
User-agent: Amazonbot
Allow: /
# AI crawlers — OAI SearchBot (OpenAI search)
User-agent: OAI-SearchBot
Allow: /
# AI crawlers — Operator (OpenAI Operator agent)
User-agent: Operator
Allow: /
# AI crawlers — Diffbot (AI knowledge graph)
User-agent: Diffbot
Allow: /
# AI crawlers — Common Crawl (used by many LLMs for training)
User-agent: CCBot
Allow: /
# AI crawlers — SonixAI
User-agent: SonixAI
Allow: /
# AI crawlers — Timpibot (AI search)
User-agent: Timpibot
Allow: /
# AI crawlers — YouBot (You.com AI search)
User-agent: YouBot
Allow: /
# AI crawlers — Omgilibot (AI data)
User-agent: omgilibot
Allow: /
# AI crawlers — iaskspider (iAsk AI)
User-agent: iaskspider
Allow: /
# Standard search engines — Yahoo / Slurp
User-agent: Slurp
Allow: /
# Standard search engines — Naver (South Korea) — Yeti
User-agent: Yeti
Allow: /
User-agent: NaverBot
Allow: /
# Standard search engines — Baidu (China)
User-agent: Baiduspider-render
Allow: /
# Standard search engines — Sogou (China)
User-agent: Sogou web spider
Allow: /
# Standard search engines — 360 Spider (China)
User-agent: 360Spider
Allow: /
# Standard search engines — Shenma / UC Web (China mobile)
User-agent: Baiduspider-mobile
Allow: /
# Standard search engines — Seznam (Czech Republic)
User-agent: SeznamBot
Allow: /
# Standard search engines — Mojeek (UK privacy search)
User-agent: MojeekBot
Allow: /
# Standard search engines — Brave Search
User-agent: BraveBot
Allow: /
# Standard search engines — Ecosia (Germany, green search)
User-agent: Ecosia
Allow: /
# Standard search engines — Qwant (France)
User-agent: Qwantify
Allow: /
# Standard search engines — Petal Search / Huawei (Arabic + Asian markets)
User-agent: PetalBot
Allow: /
# Standard search engines — Cốc Cốc (Vietnam)
User-agent: coccocbot-web
Allow: /
User-agent: coccocbot-image
Allow: /
# Standard search engines — Daum / Kakao (South Korea)
User-agent: Daumoa
Allow: /
# Standard search engines — Mail.ru / Go.Mail.ru (Russia)
User-agent: Mail.RU_Bot
Allow: /
# Standard search engines — Onet.pl (Poland)
User-agent: OnetSzukaj
Allow: /
# Standard search engines — Internet Archive / Wayback Machine
User-agent: ia_archiver
Allow: /
# Standard search engines — Googlebot News
User-agent: Googlebot-News
Allow: /
# Standard search engines — Googlebot Image
User-agent: Googlebot-Image
Allow: /
# Social media crawlers — allow for rich previews
User-agent: facebookexternalhit
Allow: /
User-agent: Twitterbot
Allow: /
User-agent: LinkedInBot
Allow: /
User-agent: WhatsApp
Allow: /
User-agent: TelegramBot
Allow: /
User-agent: Pinterestbot
Allow: /
User-agent: Slackbot
Allow: /
User-agent: Discordbot
Allow: /
# All other crawlers — allow public pages, block private paths
User-agent: *
Allow: /
Disallow: /api/
Disallow: /private/
Sitemap: https://smartg4.com/sitemap.xml
A+Domain Intelligencesmartg4.com — via GoDaddy.com, LLC, 14 years, 11 months old, hosted on CloudflarePASS
90 days
January 17, 2027
34 days
Issued by Google Trust Services
14 years, 11 months
Registered January 17, 2012
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS209242
160.153.0.223
GoDaddy.com, LLC
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
A+HTTP Probe TimingTotal 173 ms — DNS, TCP, TLS, TTFB, content transfer breakdownPASS
Connection waterfall
ACDN & DeliveryDocument and assets on CloudflarePASS
Asset hosts on a CDN
- smartg4.com — Cloudflare · assets: 48 · Cache Status: DYNAMIC
Other asset hosts
- fonts.googleapis.com — assets: 2 · below probe threshold
- img1.wsimg.com — assets: 1 · below probe threshold