Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations79 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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, 38 ms lookupPASS
| A | 104.21.12.227, 172.67.196.136 |
| AAAA | 2606:4700:3035::ac43:c488, 2606:4700:3034::6815:ce3 |
| CNAME | — |
| NS | lindsey.ns.cloudflare.com, rex.ns.cloudflare.com |
| MX | 10 eforward1.registrar-servers.com 10 eforward3.registrar-servers.com 10 eforward2.registrar-servers.com 15 eforward4.registrar-servers.com 20 eforward5.registrar-servers.com |
| TXT | google-site-verification=ZUNvuFFKGYyBRTPrSkSO_pyCqLExuOti6PqA7unLcpY SPF v=spf1 include:spf.efwd.registrar-servers.com ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ACAA Recordsissue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.comPASS
A+Multi-Resolver DNS SpeedMean 18ms across 3 resolvers (spread 28ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://filemaktab.com
282 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://filemaktab.com | 200 | 282 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 211 URLsPASS
User-agent: *
Allow: /
Disallow: /dashboard
Disallow: /api/
Sitemap: https://filemaktab.com/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefilemaktab.com — via NameCheap, Inc., 2 months oldPASS
286 days
August 22, 2027
79 days
Issued by Google Trust Services
2 months
Registered August 22, 2026
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3035::ac43:c488
NameCheap, 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