Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/2 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
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations69 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryCloudflareREVIEW
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records2 A records, 54 ms lookupPASS
| A | 172.66.167.184, 104.20.32.55 |
| AAAA | — |
| CNAME | — |
| NS | brad.ns.cloudflare.com, dina.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | google-site-verification=A5o7EMzMPJ89KTKdxrbmJ1ZoCXfd9inWmaQrH1u_rdE SPF v=spf1 include:_spf1.blackedraw.com include:_spf2.blackedraw.com include:_spf3.b... google-site-verification=gDPthQAwYV9FYj8ii5Ysg0mcP5lGrexpB64vu7rQcnU _globalsign-domain-verification=oc60Z1GZ1rDu20Ex5j6-C4z_p0u13Fp0QtvMRENUts v=extendedspf ip4:192.174.91.56 ip4:156.70.150.243 include:_netblocks.sparkpostm... _globalsign-domain-verification=XVDMsD2J-T8H9yA4omz14lxJT6zUdeqUpziuA0nr_0 |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+DNSSECSigned and validatingPASS
A+Multi-Resolver DNS SpeedMean 22ms across 3 resolvers (spread 30ms)PASS
ARedirect Chain1 redirect(s), 219 ms totalPASS
https://blackedraw.com
94 ms · HTTP/1.1
https://www.blackedraw.com/
124 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://blackedraw.com | 301 | 94 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.blackedraw.com/ | 403 | 124 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceblackedraw.com — via Dynadot Inc, 9 years, 5 months old, hosted on CloudflarePASS
2810 days
April 5, 2034
69 days
Issued by Google Trust Services
9 years, 5 months
Registered April 5, 2017
Enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
172.66.167.184
Dynadot Inc
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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