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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BHTTP Probe TimingTotal 1163 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations84 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
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records2 A records, 38 ms lookupPASS
| A | 104.21.22.72, 172.67.203.86 |
| AAAA | 2606:4700:3031::ac43:cb56, 2606:4700:3030::6815:1648 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
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 25ms across 3 resolvers (spread 37ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://www.t7mel.co
97 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.t7mel.co | 200 | 97 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 9 URLsPASS
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
User-agent: *
Allow: /
- https://www.t7mel.co/post-sitemap.xml
- https://www.t7mel.co/post-sitemap2.xml
- https://www.t7mel.co/post-sitemap3.xml
- https://www.t7mel.co/post-sitemap4.xml
- https://www.t7mel.co/page-sitemap.xml
- https://www.t7mel.co/category-sitemap.xm...
- https://www.t7mel.co/post_tag-sitemap.xm...
- https://www.t7mel.co/post_tag-sitemap2.x...
- https://www.t7mel.co/author-sitemap.xml
A+Domain Intelligencet7mel.co — via NameCheap, Inc., 7 years, 6 months oldPASS
188 days
April 24, 2027
84 days
Issued by Google Trust Services
7 years, 6 months
Registered April 24, 2019
Status unknown
Protects against DNS spoofing
Unknown
2606:4700:3031::ac43:cb56
NameCheap, Inc.
Expiry timeline
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice