red-bean.com

Checked 22 October 2026, 10:25 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 2 failed 4 info

Registration

info

.com generic · CSL Computer Service Langenbach GmbH d/b/a joker.com · expires 2030-09-13

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSL Computer Service Langenbach GmbH d/b/a joker.com
Registered
14 September 1995
Last changed
4 April 2026
Expires
13 September 2030
Status
client transfer prohibited
Registry nameservers
ns.red-bean.com, ns2.red-bean.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 2030-09-13 #3
    The registration is valid until 2030-09-13 (1421 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.

Delegation

warn

ns.red-bean.com, ns2.red-bean.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns.red-bean.com, ns2.red-bean.com
NS in the zone
ns.red-bean.com, ns2.red-bean.com
NameserverAddressesNetwork (AS)Glue
ns.red-bean.com45.79.25.59AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG45.79.25.59
ns2.red-bean.com142.93.187.14AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US142.93.187.14

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.red-bean.com, ns2.red-bean.com.
    #6
  • ✓ 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: ns.red-bean.com, ns2.red-bean.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 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 1 address; AS63949 (AKAMAI-LINODE-AP - Akamai Connected Cloud, SG): 1 address.
  • 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

fail

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.red-bean.com 45.79.25.59NOERROR, 124 ms, authoritativenoyes / yesrefused9.20.30-1~deb13u1-Debian
ns2.red-bean.com 142.93.187.14SERVFAIL, 93 ms, NOT authoritativenono / yesrefused9.20.29-1-Debian

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns2.red-bean.com (142.93.187.14): SERVFAIL, authoritative=false.
    #15
  • ✓ 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.red-bean.com: "9.20.30-1~deb13u1-Debian"; ns2.red-bean.com: "9.20.29-1-Debian". 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: ns2.red-bean.com (142.93.187.14): read tcp 46.225.38.91:60514->142.93.187.14:53: read: connection reset by peer.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026081001 · primary ns.red-bean.com

Found

Primary (MNAME)
ns.red-bean.com
Contact (RNAME)
root.red-bean.com
Serial
2026081001
Refresh / retry
3600 s / 900 s
Expire
604800 s
Negative TTL
3600 s

Checks

  • ✓ Serial 2026081001 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.red-bean.com is one of the listed nameservers.
  • ✓ Contact root@red-bean.com #25
    The SOA RNAME root.red-bean.com means root@red-bean.com.
  • ✓ Date-based serial #26
    The serial 2026081001 follows the YYYYMMDDnn convention (2026-08-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

info

8 records at the apex

Found

Read from
45.79.25.59:53
TypeValueTTL
SOAns.red-bean.com. root.red-bean.com. 2026081001 3600 900 604800 36003600
NSns.red-bean.com.3600
NSns2.red-bean.com.3600
A45.79.25.593600
MX0 mx-red-bean-com.red-bean.com.3600
TXT"v=spf1 ip4:45.79.25.59 ip6:2600:3c00::f03c:91ff:fe7e:d702 include:_spf.google.com ~all"3600
TXT"google-site-verification=EKV9HG3wKZ9r8S68xU6AiDP0alVhqp94Yd-00mVdI0E"3600
TXT"google-site-verification=jLvdtAIYUVlvLc5z08bJJuOVApJaDLwbRlO7J19QPNw"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 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