vocaroo.com

Checked 22 October 2026, 11:22 UTC · via 8.8.8.8
✗Problems found
21 passed 4 warnings 1 failed 5 info

Registration

info

.com generic · Mesh Digital Limited · expires 2028-10-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Mesh Digital Limited
Registered
3 October 2007
Last changed
19 September 2026
Expires
3 October 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns.heartinternet.uk, ns2.heartinternet.uk
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-10-03 #3
    The registration is valid until 2028-10-03 (712 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.

Delegation

warn

ns.heartinternet.uk, ns2.heartinternet.uk

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns.heartinternet.uk, ns2.heartinternet.uk
NS in the zone
ns.heartinternet.uk, ns2.heartinternet.uk
NameserverAddressesNetwork (AS)Glue
ns.heartinternet.uk79.170.40.2AS20738 GD-EMEA-DC-LD5 - Heart Internet limited, GB-
ns2.heartinternet.uk79.170.43.3AS20738 GD-EMEA-DC-LD5 - Heart Internet limited, GB-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.heartinternet.uk, ns2.heartinternet.uk.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS20738 (GD-EMEA-DC-LD5 - Heart Internet limited, GB): 2 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 .uk
    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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.heartinternet.uk 79.170.40.2NOERROR, 25 ms, authoritativenono / norefusedServed by POWERDNS 3.1 $Id: packethandler.cc 2579 2012-04-26 11:28:04Z peter $
ns2.heartinternet.uk 79.170.43.3NOERROR, 25 ms, authoritativenono / norefusedServed by POWERDNS 3.1 $Id: packethandler.cc 2579 2012-04-26 11:28:04Z peter $

Checks

  • ✓ All respond #14
    All 2 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: ns.heartinternet.uk: "Served by POWERDNS 3.1 $Id: packethandler.cc 2579 2012-04-26 11:28:04Z peter $"; ns2.heartinternet.uk: "Served by POWERDNS 3.1 $Id: packethandler.cc 2579 2012-04-26 11:28:04Z peter $". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns.heartinternet.uk (79.170.40.2): read tcp 46.225.38.91:35254->79.170.40.2:53: i/o timeout; ns2.heartinternet.uk (79.170.43.3): read tcp 46.225.38.91:38254->79.170.43.3:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns.heartinternet.uk (79.170.40.2), ns2.heartinternet.uk (79.170.43.3).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026061838 · primary ns.heartinternet.uk

Found

Primary (MNAME)
ns.heartinternet.uk
Contact (RNAME)
hostmaster.mainnameserver.com
Serial
2026061838
Refresh / retry
10800 s / 600 s
Expire
2419200 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.heartinternet.uk (79.170.40.2)2026061838
ns2.heartinternet.uk (79.170.43.3)2026061838

Checks

  • ✓ Serial 2026061838 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 10m, expire 28d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.heartinternet.uk is one of the listed nameservers.
  • ✓ Contact hostmaster@mainnameserver.com #25
    The SOA RNAME hostmaster.mainnameserver.com means hostmaster@mainnameserver.com.
  • ✓ Date-based serial #26
    The serial 2026061838 follows the YYYYMMDDnn convention (2026-06-18).

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

info

11 records at the apex

Found

Read from
79.170.40.2:53
TypeValueTTL
SOAns.heartinternet.uk. hostmaster.mainnameserver.com. 2026061838 10800 600 2419200 36003600
NSns.heartinternet.uk.3600
NSns2.heartinternet.uk.3600
A78.47.172.2303600
A78.47.84.1573600
AAAA2a01:4f8:c2c:f976::13600
AAAA2a01:4f8:c010:37ff::13600
MX10 in1-smtp.messagingengine.com.3600
MX20 in2-smtp.messagingengine.com.3600
TXT"google-site-verification=7oLGrnKWNbDfOqJ6kFbC9qA_beiJFNeZfsVH8cmk2ng"3600
TXT"v=spf1 include:spf.messagingengine.com include:lists.xzist.org include:amazonses.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ 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