Skip to content
https://okinawa.dearswedding-resort.jp

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
10
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 10 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2103 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
274 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
264 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
266 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.98 s
Total Time Total request time from DNS lookup through full response.
2.10 s

Connection waterfall

DNS Lookup 274 ms TCP Connect 264 ms TLS Handshake 266 ms Server Processing 1.18 s Content Transfer 123 ms
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 269 ms lookup
REVIEW
1 A records, 269 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.43.94.61
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (269 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 269 ms
A162.43.94.61
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 269 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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)

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 162.43.94.61 does not match any cert SAN: sv15060.xserver.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
Multi-Resolver DNS Speed
Action
Mean 330ms across 3 resolvers (spread 226ms)
REVIEW
Mean 330ms across 3 resolvers (spread 226ms)
Info::
Google: 252ms
Got: 252ms via 8.8.8.8:53
Info::
Quad9: 262ms
Got: 262ms via 9.9.9.9:53
Info::
Cloudflare: 478ms
Got: 478ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 226ms (min 252ms / max 478ms)
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.
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
59 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
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::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://okinawa.dearswedding-resort.jp

https://okinawa.dearswedding-resort.jp

1568 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://okinawa.dearswedding-resort.jp2001568 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 80 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 80 B Sitemaps referenced 0 User-agents * Sitemap: https://okinawa.dearswedding-resort.jp/sitemap_index.xml Blocking No — crawling allowed
User-agent: * Sitemap: https://okinawa.dearswedding-resort.jp/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.okinawa.dearswedding-resort.jp/
200https://okinawa.dearswedding-resort.jp/

HTTP → HTTPS

301http://okinawa.dearswedding-resort.jp/ → https://okinawa.dearswedding-resort.jp/

Consistent

A+
Domain Intelligence
dearswedding-resort.jp — hosted on XSERVER Xserver Inc., JP
PASS
dearswedding-resort.jp — hosted on XSERVER Xserver Inc., JP
Info::
Hosting: XSERVER Xserver Inc., JP
Got: AS131965
Domain expiry

Unknown

SSL certificate

59 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

XSERVER Xserver Inc., JP

ASN AS131965

162.43.94.61

Registrar

Registrar unknown

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Name Servers ns1.xserver.jp, ns2.xserver.jp, ns3.xserver.jp, ns4.xserver.jp, ns5.xserver.jp
Hosting
IP Address 162.43.94.61
ASN AS131965 (XSERVER Xserver Inc., JP)
Provider XSERVER Xserver Inc., JP
Data source: whois (1.6s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback