vegas.com

Checked 22 October 2026, 11:21 UTC · via 8.8.8.8
!Passed with warnings
24 passed 4 warnings 0 failed 3 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2028-08-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
17 August 1998
Last changed
15 July 2026
Expires
16 August 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.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 2028-08-16 #3
    The registration is valid until 2028-08-16 (663 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.com
NS in the zone
ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.com
NameserverAddressesNetwork (AS)Glue
ns1.vegas.com193.108.91.33AS20940 AKAMAI-ASN1 - Akamai International B.V., NL193.108.91.33
ns2.vegas.com184.26.161.66AS21342 AKAMAI-ASN2 - Akamai International B.V., NL184.26.161.66
ns3.vegas.com95.101.36.67AS21342 AKAMAI-ASN2 - Akamai International B.V., NL95.101.36.67
ns4.vegas.com2.16.130.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL2.16.130.64
ns5.vegas.com95.100.168.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL95.100.168.65
ns6.vegas.com23.61.199.66AS21342 AKAMAI-ASN2 - Akamai International B.V., NL23.61.199.66

Checks

  • ✓ 6 nameservers #6
    Delegated to ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.vegas.com, ns2.vegas.com, ns3.vegas.com, ns4.vegas.com, ns5.vegas.com, ns6.vegas.com.
  • ✓ 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 6 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 5 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vegas.com 193.108.91.33NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
ns2.vegas.com 184.26.161.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
ns3.vegas.com 95.101.36.67NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
ns4.vegas.com 2.16.130.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.33
ns5.vegas.com 95.100.168.65NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
ns6.vegas.com 23.61.199.66NOERROR, 7 ms, authoritativenoyes / yesrefused41824.5

Checks

  • ✓ All respond #14
    All 6 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.vegas.com: "41824.4"; ns2.vegas.com: "48878.32"; ns3.vegas.com: "48878.26"; ns4.vegas.com: "48878.33"; ns5.vegas.com: "41824.4"; ns6.vegas.com: "41824.5". Hide or replace the version string.
    #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.

SOA

pass

serial 2026102000 · primary ns2.vegas.com

Found

Primary (MNAME)
ns2.vegas.com
Contact (RNAME)
hostmaster.vegas.com
Serial
2026102000
Refresh / retry
3600 s / 600 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.vegas.com (193.108.91.33)2026102000
ns2.vegas.com (184.26.161.66)2026102000
ns3.vegas.com (95.101.36.67)2026102000
ns4.vegas.com (2.16.130.64)2026102000
ns5.vegas.com (95.100.168.65)2026102000
ns6.vegas.com (23.61.199.66)2026102000

Checks

  • ✓ Serial 2026102000 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.vegas.com is one of the listed nameservers.
  • ✓ Contact hostmaster@vegas.com #25
    The SOA RNAME hostmaster.vegas.com means hostmaster@vegas.com.
  • ✓ Date-based serial #26
    The serial 2026102000 follows the YYYYMMDDnn convention (2026-10-20).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

23 records at the apex

Found

Read from
193.108.91.33:53
TypeValueTTL
SOAns2.vegas.com. hostmaster.vegas.com. 2026102000 3600 600 1209600 30086400
NSns1.vegas.com.600
NSns4.vegas.com.600
NSns5.vegas.com.600
NSns6.vegas.com.600
NSns3.vegas.com.600
NSns2.vegas.com.600
A2.16.183.1720
A2.16.183.1820
MX10 vegas-com.mail.protection.outlook.com.600
TXT"google-site-verification=aoPPQ4YNrxmTZKczntfNpXTBekZDsWKlJh2R7FSfo98"600
TXT"google-site-verification=TKud1H3jNfjR-c_nqXXxx_vDVa9wN_g9RiUbpwAVGu0"600
TXT"MS=ms39532384"600
TXT"anthropic-domain-verification-z8ay9s=sqlCLFu7F0ZW7eCMIyopgGeYh"600
TXT"facebook-domain-verification=pk0vdcz9iu0z4ylrdfms1duhscwfgp"600
TXT"atlassian-domain-verification=1n32eZV49BBrujOf6kKt6QBu4fLYELLFbspgUKyiWOp6pxi04ASiHPfaDPtV1mt1"600
TXT"cursor-domain-verification-7qt2hh=lyDAIWqaovbUr6JW6RAhPu6k8"600
TXT"v=spf1 ip4:192.5.73.0/24 ip4:199.255.252.0/22 ip4:66.244.67.33 ip4:66.244.67.50 include:trustpilotservice.com a:mycoionline.com include:spf.protection.outlook.com include:mail.zendesk.com ip4:159.183.116.99 ip4:134.128.79.180 ip4:134.128.98.148 -all"600
TXT"google-site-verification=zN0HarMecOA7qv15FBgefphq3QA1LgzQzFT6QceJ1XY"600
TXT"figma-domain-verification=06fe666b39fbbf49910c11e44ea9d41d3cfd5f00aca27a4888a4642279cb0ada-1762985859"600
TXT"SFMC-H4F3gErYqDO72lyQOEiVVOElOr88vqhy0ToV-IC1"600
TXT"perplexity-ai-domain-verification-hyxaee=lXLSZTxkwIpyV7UOcYrp3snKv"600
TXT"slack-domain-verification=mxYC74rzDPcBZkWVzK9m7bk1R0RxtuMnZCJ5vMiB"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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