viracut.app 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 viracut.app 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::258 no answer✗ 2600:1f18:16e:df01::259 no answer	broken
www over IPv6 www.viracut.app 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 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. sage.ns.cloudflare.com ✓tess.ns.cloudflare.com ✓	yes

What's keeping viracut.app from an A

Fix or remove the AAAA record for viracut.app
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.viracut.app
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

viracut.app Has IPv6

A (IPv4)	98.84.224.111 18.208.88.157
AAAA (IPv6)	2600:1f18:16e:df01::258 2600:1f18:16e:df01::259

www.viracut.app Has IPv6

Alias of	viral-video-editor.netlify.app
A (IPv4)	18.208.88.157 98.84.224.111
AAAA (IPv6)	2600:1f18:16e:df01::259 2600:1f18:16e:df01::258

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: viracut.app
Measured 2026-11-07 22:40:42 UTC by aaaa.bot (one server on Fly.io, region iad)

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

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: viracut.app 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::258: no answer
    2600:1f18:16e:df01::259: no answer
- www over IPv6: www.viracut.app 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: 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/j7wlaI1Iu7

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

Checked 2026-11-07 22:40:42 UTC. Full DNS report: dns.pizza/domain/viracut.app · Age, certificate and blocklists: how.is/viracut.app · JSON: /api/v1/viracut.app