Yes — platebyplate.fit has IPv6.

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

This is a saved measurement from 2026-11-10 16:00 UTC. Check platebyplate.fit live now

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 platebyplate.fit has an AAAA record and answers on it. ✓ 2a02:4780:75:8cdc::1 answers · 443	yes
www over IPv6 www.platebyplate.fit has an AAAA record and answers on it. ✓ 2a02:4780:75:8cdc::1 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
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

HTTPS over IPv6 · not part of the grade yet
Redirects to linktr.ee, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.

https://platebyplate.fit/ via 2a02:4780:75:8cdc::1 → 302https://linktr.ee/platebyplatezo · redirects to linktr.ee, which has no IPv6 address

problem

What's keeping platebyplate.fit from an A

A redirect leads off IPv6
Redirects to linktr.ee, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all. Give the redirect target IPv6 too, or redirect somewhere that has it.
Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

platebyplate.fit Has IPv6

A (IPv4)	2.24.73.102
AAAA (IPv6)	2a02:4780:75:8cdc::1

www.platebyplate.fit Has IPv6

A (IPv4)	2.24.73.102
AAAA (IPv6)	2a02:4780:75:8cdc::1

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: platebyplate.fit
Measured 2026-11-10 16:00:12 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    2.24.73.102
AAAA (IPv6): 2a02:4780:75:8cdc::1
www AAAA:    2a02:4780:75:8cdc::1

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: platebyplate.fit has an AAAA record and answers on it.
    2a02:4780:75:8cdc::1: answers (TCP 443)
- www over IPv6: www.platebyplate.fit has an AAAA record and answers on it.
    2a02:4780:75:8cdc::1: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers 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).

HTTPS over IPv6 (not graded): Redirects to linktr.ee, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.
    https://platebyplate.fit/ via 2a02:4780:75:8cdc::1 -> HTTP 302, certificate: valid
    https://linktr.ee/platebyplatezo (redirects to linktr.ee, which has no IPv6 address)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/_ReeEAfTxh

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

Checked 2026-11-10 16:00:12 UTC. Full DNS report: dns.pizza/domain/platebyplate.fit · Age, certificate and blocklists: how.is/platebyplate.fit · JSON: /api/v1/platebyplate.fit