rayportal.bond publishes IPv6 but doesn't answer on it.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

IPv6 readiness

Publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 rayportal.bond has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2604:a880:800:14:0:1:225d:c000 no answer	broken
www over IPv6 www.rayportal.bond has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2604:a880:800:14:0:1:225d:c000 no answer	broken
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. greg.ns.cloudflare.com ✓jillian.ns.cloudflare.com ✓	yes

What's keeping rayportal.bond from an A

Fix or remove the AAAA record for rayportal.bond
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.
Fix or remove the AAAA record for www.rayportal.bond
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

rayportal.bond Has IPv6

A (IPv4)	159.203.143.218
AAAA (IPv6)	2604:a880:800:14:0:1:225d:c000

www.rayportal.bond Has IPv6

A (IPv4)	159.203.143.218
AAAA (IPv6)	2604:a880:800:14:0:1:225d:c000

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

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

IPv6 measurement: rayportal.bond
Measured 2026-11-04 07:49:07 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    159.203.143.218
AAAA (IPv6): 2604:a880:800:14:0:1:225d:c000
www AAAA:    2604:a880:800:14:0:1:225d:c000

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: rayportal.bond has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2604:a880:800:14:0:1:225d:c000: no answer
- www over IPv6: www.rayportal.bond has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2604:a880:800:14:0:1:225d:c000: no answer
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It 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/V9qlF_5DPu

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

Checked 2026-11-04 07:49:07 UTC. Full DNS report: dns.pizza/domain/rayportal.bond · Age, certificate and blocklists: how.is/rayportal.bond · JSON: /api/v1/rayportal.bond