Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DMulti-Resolver DNS SpeedActionMean 338ms across 3 resolvers (spread 752ms)FIX
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
BHTTP Probe TimingTotal 1127 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations60 days until leaf cert expires — 2 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
CCDN & DeliveryActionAssets on Cloudflare (host blog.arkw.co.jp, 3 assets); document served directly from originREVIEW
Asset hosts on a CDN
- blog.arkw.co.jp — Cloudflare · assets: 3 · Cache Status: HIT
Other asset hosts
- www.clarity.ms — assets: 6 · Microsoft Azure
- fonts.googleapis.com — assets: 2 · below probe threshold
- www.googletagmanager.com — assets: 2 · below probe threshold
- js-na2.hs-analytics.net — assets: 1 · below probe threshold
- js-na2.hs-banner.com — assets: 1 · below probe threshold
- js-na2.hs-scripts.com — assets: 1 · below probe threshold
- js-na2.hscollectedforms.net — assets: 1 · below probe threshold
- js-na2.hubspot.com — assets: 1 · below probe threshold
- js-na2.usemessages.com — assets: 1 · below probe threshold
- scripts.clarity.ms — assets: 1 · below probe threshold
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records1 A records, 2 ms lookupPASS
| A | 112.78.125.117 |
| AAAA | — |
| CNAME | arkw.co.jp |
| NS | ns1.dns.ne.jp, ns2.dns.ne.jp |
| MX | 0 arkw-co-jp.mail.protection.outlook.com |
| TXT | SPF v=spf1 include:spf.protection.outlook.com include:4473934.spf04.hubspotemail.net... |
| 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+Redirect ChainNo redirects — direct accessPASS
https://www.arkw.co.jp
885 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.arkw.co.jp | 200 | 885 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 96 URLsPASS
User-agent: *
Disallow: /arkw_www3/
Disallow: /resale/
Sitemap: https://www.arkw.co.jp/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
Domain IntelligenceDomain intelligence data not availableINFO
RDAP and WHOIS lookup both failed