mobile.usc.edu publishes IPv6 but doesn't answer on it.

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

This is a saved measurement from 2026-11-03 08:04 UTC. Check mobile.usc.edu live now

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
mobile.usc.edu's AAAA record points at an address that isn't on the public internet, so IPv6 visitors can't reach it.
✗ aaaa:2620:12a:8000::1 not public✗ aaaa:2620:12a:8001::1 not public
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
4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns-1466.awsdns-55.org ✓ns-1798.awsdns-32.co.uk ✓ns-368.awsdns-46.com ✓ns-549.awsdns-04.net ✓
yes

What's keeping mobile.usc.edu from an A

  1. Fix or remove the AAAA record for mobile.usc.edu
    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

mobile.usc.edu  Has IPv6

A (IPv4)23.185.0.1
AAAA (IPv6)aaaa:2620:12a:8000::1
aaaa:2620:12a:8001::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

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

Checked 2026-11-03 08:04:40 UTC. Full DNS report: dns.pizza/domain/mobile.usc.edu · Age, certificate and blocklists: how.is/mobile.usc.edu · JSON: /api/v1/mobile.usc.edu