After a server move, one phone may reach the new site while another still sees a parking page. The two clients may be using different recursive resolvers. Each resolver can keep an older answer until its cached TTL expires.

sh
dig +short example.com NS
dig +noall +answer @ns1.example.net www.example.com A
dig +noall +answer www.example.com A
dig +noall +answer www.example.com AAAA

Replace the example nameserver with one from the first command. The direct query tells you what that authoritative server serves. The query without an explicit server reflects the resolver configured on your machine. Compare the answer and its remaining TTL. If the authoritative servers disagree, check the DNS provider before waiting on caches.

Trace the full hostname

The apex and www are separate names. IPv4 and IPv6 can also lead a browser to different endpoints. Check aliases and remove an obsolete AAAA record only after confirming which host should handle IPv6. Lowering TTL ahead of a migration can shorten the cutover window once the previous TTL has passed.

Finally open the real URL and check what certificate and page come back. An address record can point to the right IP while the web server still selects the wrong virtual host.

References