veoh.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-06-24

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
24 June 2005
Last changed
24 June 2026
Expires
24 June 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns-1.big1cloud.net, ns-2.big1cloud.net, ns-3.big1cloud.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-06-24 #3
    The registration is valid until 2027-06-24 (244 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns-1.big1cloud.net, ns-2.big1cloud.net, ns-3.big1cloud.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns-1.big1cloud.net, ns-2.big1cloud.net, ns-3.big1cloud.net
NS in the zone
ns-1.big1cloud.net, ns-2.big1cloud.net, ns-3.big1cloud.net
NameserverAddressesNetwork (AS)Glue
ns-1.big1cloud.net199.34.243.75AS7979 SERVERS-COM - Servers.com, Inc., US-
ns-2.big1cloud.net199.34.243.76AS7979 SERVERS-COM - Servers.com, Inc., US-
ns-3.big1cloud.net199.34.243.77AS7979 SERVERS-COM - Servers.com, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns-1.big1cloud.net, ns-2.big1cloud.net, ns-3.big1cloud.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 one network
    all IPv4 addresses are in 199.34.243.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS7979 (SERVERS-COM - Servers.com, Inc., US): 3 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-1.big1cloud.net 199.34.243.75NOERROR, 164 ms, authoritativenoyes / yesrefused-
ns-2.big1cloud.net 199.34.243.76NOERROR, 164 ms, authoritativenoyes / yesrefused-
ns-3.big1cloud.net 199.34.243.77NOERROR, 161 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

info

serial 2026101002 · primary veoh.com

Found

Primary (MNAME)
veoh.com
Contact (RNAME)
postmaster.veoh.com
Serial
2026101002
Refresh / retry
10380 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns-1.big1cloud.net (199.34.243.75)2026101002
ns-2.big1cloud.net (199.34.243.76)2026101002
ns-3.big1cloud.net (199.34.243.77)2026101002

Checks

  • ✓ Serial 2026101002 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 173m, retry 1h, expire 7d, negative TTL 10m.
  • i
    Hidden master
    The primary nameserver veoh.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact postmaster@veoh.com #25
    The SOA RNAME postmaster.veoh.com means postmaster@veoh.com.
  • ✓ Date-based serial #26
    The serial 2026101002 follows the YYYYMMDDnn convention (2026-10-10).

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

12 records at the apex

Found

Read from
199.34.243.75:53
TypeValueTTL
SOAveoh.com. postmaster.veoh.com. 2026101002 10380 3600 604800 600600
NSns-3.big1cloud.net.3600
NSns-1.big1cloud.net.3600
NSns-2.big1cloud.net.3600
A104.244.97.2016
MX10 alt3.aspmx.l.google.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
MX10 alt4.aspmx.l.google.com.300
MX1 aspmx.l.google.com.300
TXT"google-site-verification=lOxn_UuBjTRzKDVv_PIFpC6y9zHAqtsYOvHt3r9o9UE"300
TXT"v=spf1 ip4:208.71.104.0/24 include:dc-aa8e722993._spfm.veoh.com ~all"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (16s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1h; 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