Skip to content
https://www.arkw.co.jp

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
10
PASS
4
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
4 PASS 10 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 593ms across 3 resolvers (spread 1203ms)
FIX
Mean 593ms across 3 resolvers (spread 1203ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 538ms
Got: 538ms via 9.9.9.9:53
Info::
Cloudflare: 1223ms
Got: 1223ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 1203ms (min 20ms / max 1223ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
HTTP Probe Timing
Action
Total 2493 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
777 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
285 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
287 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.21 s
Total Time Total request time from DNS lookup through full response.
2.49 s

Connection waterfall

DNS Lookup 777 ms TCP Connect 285 ms TLS Handshake 287 ms Server Processing 860 ms Content Transfer 285 ms
B
DNS Records
1 A records, 286 ms lookup
REVIEW
1 A records, 286 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 112.78.125.117
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: arkw.co.jp
Info::
2 nameserver(s) configured
Got: ns2.dns.ne.jp, ns1.dns.ne.jp
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (286 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 286 ms
A112.78.125.117
AAAA—
CNAMEarkw.co.jp
NSns2.dns.ne.jp, ns1.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...
CAALookup not available with standard resolver
Resolved in 286 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 112.78.125.117 does not match any cert SAN: www657b.sakura.ne.jp
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

60
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
C
CDN & Delivery
Action
Assets on Cloudflare (host blog.arkw.co.jp, 3 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host blog.arkw.co.jp, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (blog.arkw.co.jp, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a5ccc53bf901cfb5-MAD
Info::
Assets on Cloudflare: blog.arkw.co.jp (assets: 3), cache HIT
Got: cf-ray: a5ccc53bf901cfb5-MAD
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

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.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.arkw.co.jp

https://www.arkw.co.jp

1366 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.arkw.co.jp2001366 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 96 URLs
PASS
robots.txt present, sitemap with 96 URLs
Info::
robots.txt is present
Got: 105 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 96 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 105 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /arkw_www3/

Disallow: /resale/


Sitemap: https://www.arkw.co.jp/sitemap.xml


A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.arkw.co.jp/
301https://arkw.co.jp/

Preferred variant: www

HTTP → HTTPS

301http://www.arkw.co.jp/ → https://www.arkw.co.jp/

Consistent

Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback