No — tokyomedicalequipmentslimited.com is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

This is a saved measurement from 2026-11-15 14:41 UTC. Check tokyomedicalequipmentslimited.com live now

IPv6 readiness

The www address publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 tokyomedicalequipmentslimited.com has no AAAA record.	no
www over IPv6 www.tokyomedicalequipmentslimited.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2600:1f18:16e:df01::259 no answer✗ 2600:1f18:16e:df01::258 no answer	broken
Mail servers (MX) have IPv6 Every mail server has an AAAA record. smtp.google.com ✓	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. dns1.registrar-servers.com ✓dns2.registrar-servers.com ✓	yes

What's keeping tokyomedicalequipmentslimited.com from an A

Give tokyomedicalequipmentslimited.com an IPv6 address
Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
Fix or remove the AAAA record for www.tokyomedicalequipmentslimited.com
Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.

Check again

tokyomedicalequipmentslimited.com IPv4 only

A (IPv4)	75.2.60.5
AAAA (IPv6)	none

www.tokyomedicalequipmentslimited.com Has IPv6

Alias of	teal-gumption-7cbb22.netlify.app
A (IPv4)	18.208.88.157 98.84.224.111
AAAA (IPv6)	2600:1f18:16e:df01::259 2600:1f18:16e:df01::258

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: tokyomedicalequipmentslimited.com
Measured 2026-11-15 14:41:52 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    75.2.60.5
AAAA (IPv6): none
www AAAA:    2600:1f18:16e:df01::259, 2600:1f18:16e:df01::258

Readiness grade F: The www address publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: tokyomedicalequipmentslimited.com has no AAAA record.
- www over IPv6: www.tokyomedicalequipmentslimited.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2600:1f18:16e:df01::259: no answer
    2600:1f18:16e:df01::258: no answer
- Mail servers (MX) have IPv6: Every mail server has an AAAA record.
- Nameservers have IPv6: 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/oV_lwP9Nfs

Permanent link: aaaa.bot/r/oV_lwP9Nfs · How we measure

Checked 2026-11-15 14:41:52 UTC. Full DNS report: dns.pizza/domain/tokyomedicalequipmentslimited.com · Age, certificate and blocklists: how.is/tokyomedicalequipmentslimited.com · JSON: /api/v1/tokyomedicalequipmentslimited.com