regus.com

.com generic · CSC Corporate Domains, Inc. · expires 2027-03-30

Found

TLD

.com (generic)

ICANN policies apply

yes

Registrar

CSC Corporate Domains, Inc.

Registered

29 March 1996

Last changed

26 March 2026

Expires

30 March 2027

Status

client transfer prohibited

Registry nameservers

ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net

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-03-30 #3

  The registration is valid until 2027-03-30 (158 days).
• ✓ Transfer locked #4

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

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

ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net

Found

Parent zone

com

Delegation from

a.gtld-servers.net (192.5.6.30)

NS at the parent

ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net

NS in the zone

ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net

Checks

• ✓ 4 nameservers #6

  Delegated to ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net.
• ✓ 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.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS12008 (VERCARA - Vercara, LLC, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• i

  All nameserver names under .net

  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.

8 of 8 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 8 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.netnames.net: "UltraDNS Nameserver"; ns2.netnames.net: "UltraDNS Nameserver"; ns5.netnames.net: "UltraDNS Nameserver"; ns6.netnames.net: "UltraDNS Nameserver".

  #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.

24 records at the apex

Found

Read from

156.154.130.100:53

Checks

• ✓ TTLs within range #32

  TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
• ✓ No CNAME at the apex #33

  The zone apex has no CNAME record.
• i

  Wildcard record

  A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

  #34
• i

  No CAA records

  Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

  #35