altavista.com

.com generic · MarkMonitor Inc. · expires 2027-09-08

Found

TLD

.com (generic)

ICANN policies apply

yes

Registrar

MarkMonitor Inc.

Registered

9 September 1998

Last changed

7 August 2026

Expires

8 September 2027

Status

client delete prohibited, client transfer prohibited, client update prohibited

Registry nameservers

ns1.yahoo.com, ns2.yahoo.com

RDAP server

https://rdap.verisign.com/com/v1/

Checks

• i

  .com is a generic TLD (gTLD)

  Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.

  #1
• ✓ TLD delegated and signed #2

  .com is delegated in the root zone and DNSSEC-signed.
• ✓ Expires on 2027-09-08 #3

  The registration is valid until 2027-09-08 (320 days).
• ✓ Transfer locked #4

  Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
• ✓ Registry and delegation match #5

  The nameservers registered at the registry are the ones published in DNS.

ns1.yahoo.com, ns2.yahoo.com

Found

Parent zone

com

Delegation from

a.gtld-servers.net (192.5.6.30)

NS at the parent

ns1.yahoo.com, ns2.yahoo.com

NS in the zone

ns1.yahoo.com, ns2.yahoo.com

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.yahoo.com, ns2.yahoo.com.

  #6
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ No glue needed #8

  All nameservers are outside the zone, so no glue records are needed.
• ✓ All names resolve #9

  Every nameserver name has an address and is not an alias.
• ✓ Nameservers in different networks #10

  The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
• ✓ 3 autonomous systems #11

  The nameservers are spread over: AS10310 (YAHOO-1 - Yahoo Holdings Inc., US): 1 address; AS10880 (YAHOO-AN2 - Yahoo Holdings Inc., US): 1 address; AS7280 (YAHOO-FC - Yahoo Holdings Inc., US): 2 addresses.
• i

  All nameserver names under .com

  All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

  #12
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

4 of 4 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 4 nameserver addresses answered.
• ✓ All authoritative #15

  Every responding nameserver answers authoritatively for the zone.
• ✓ No recursion #16

  The nameservers do not answer recursive queries for other domains.
• i

  Identifying string disclosed

  These nameservers answer version queries with a string that is not a version number: ns1.yahoo.com: "Yahoo"; ns2.yahoo.com: "Yahoo".

  #17
• ✓ Zone transfers refused #18

  No nameserver allows a zone transfer to the public.
• ✓ TCP supported #19

  All nameservers answer over TCP.
• ✓ EDNS supported #20

  All nameservers support EDNS(0).
• ✓ Public addresses #21

  All nameserver addresses are publicly routable.

serial 2026080501 · primary ns-admin.altavista.com

Found

Primary (MNAME)

ns-admin.altavista.com

Contact (RNAME)

dns-technical.av.com

Serial

2026080501

Refresh / retry

3600 s / 300 s

Expire

604800 s

Negative TTL

7200 s

Serial per nameserver

Checks

• ✓ Serial 2026080501 everywhere #22

  All nameservers serve the same version of the zone.
• ✓ Timers within recommendations #23

  SOA refresh 1h, retry 5m, expire 7d, negative TTL 2h.
• i

  Hidden master (not resolvable)

  The primary nameserver ns-admin.altavista.com is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.

  #24
• ✓ Contact dns-technical@av.com #25

  The SOA RNAME dns-technical.av.com means dns-technical@av.com.
• ✓ Date-based serial #26

  The serial 2026080501 follows the YYYYMMDDnn convention (2026-08-05).