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
CReverse DNSAction0/4 IPs match cert SANREVIEW
BHTTP Probe TimingTotal 1085 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations69 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
A+DNS Records2 A records, 37 ms lookupPASS
| A | 104.21.78.48, 172.67.216.151 |
| AAAA | 2606:4700:3032::6815:4e30, 2606:4700:3033::ac43:d897 |
| CNAME | — |
| NS | mike.ns.cloudflare.com, oaklyn.ns.cloudflare.com |
| MX | 16 route3.mx.cloudflare.net 47 route1.mx.cloudflare.net 90 route2.mx.cloudflare.net |
| TXT | google-site-verification=dBvfys9i1n_OLQtaCvNrvzj-QnlJQcp79gkeLmcuSSY SPF v=spf1 include:_spf.mx.cloudflare.net ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 18ms across 3 resolvers (spread 26ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://mekawire.com
1030 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://mekawire.com | 200 | 1030 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
User-Agent: AhrefsBot
User-Agent: AhrefsSiteAudit
User-Agent: SemrushBot
User-Agent: SiteAuditBot
User-Agent: MJ12bot
User-Agent: DotBot
User-Agent: BLEXBot
User-Agent: DataForSeoBot
User-Agent: serpstatbot
User-Agent: barkrowler
Disallow: /
User-Agent: Googlebot
User-Agent: Google-Extended
User-Agent: Bingbot
User-Agent: Yeti
User-Agent: Daumoa
User-Agent: Applebot
User-Agent: Applebot-Extended
User-Agent: DuckDuckBot
User-Agent: OAI-SearchBot
User-Agent: ChatGPT-User
User-Agent: GPTBot
User-Agent: PerplexityBot
User-Agent: Perplexity-User
User-Agent: ClaudeBot
User-Agent: Claude-SearchBot
User-Agent: Claude-User
Allow: /
Disallow: /api/
Disallow: /search
Disallow: /admin
User-Agent: *
Allow: /
Disallow: /api/
Disallow: /search
Disallow: /admin
Sitemap: https://mekawire.com/sitemap.xml
Sitemap: https://mekawire.com/news-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencemekawire.com — via Cloudflare, Inc., 20 days oldPASS
338 days
October 13, 2027
69 days
Issued by Let's Encrypt
20 days
Registered October 13, 2026
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3033::ac43:d897
Cloudflare, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Newly registered domain — build backlinks and content to establish SEO trust
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Informational: domain age. Newer domains may have lower trust signals in spam/security filters.
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