renderosity.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-10-12

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
12 October 1999
Last changed
15 October 2026
Expires
12 October 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
dns1.bondware.com, dns2.bondware.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 2027-10-12 #3
    The registration is valid until 2027-10-12 (355 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

dns1.bondware.com, dns2.bondware.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.bondware.com, dns2.bondware.com
NS in the zone
dns1.bondware.com, dns2.bondware.com
NameserverAddressesNetwork (AS)Glue
dns1.bondware.com52.5.104.98AS16509 AMAZON-02 - Amazon.com, Inc., US52.5.104.98
dns2.bondware.com52.70.244.197AS14618 AMAZON-AES - Amazon.com, Inc., US52.70.244.197

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.bondware.com, dns2.bondware.com.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14618 (AMAZON-AES - Amazon.com, Inc., US): 1 address; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 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

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.bondware.com 52.5.104.98NOERROR, 98 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 3.3.3 (jenkins@autotest.powerdns.com built 20161031213210 mockbuild@)
dns2.bondware.com 52.70.244.197NOERROR, 98 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 3.3.3 (jenkins@autotest.powerdns.com built 20150610125050 mockbuild@)

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: dns1.bondware.com: "PowerDNS Authoritative Server 3.3.3 (jenkins@autotest.powerdns.com built 20161031213210 mockbuild@)"; dns2.bondware.com: "PowerDNS Authoritative Server 3.3.3 (jenkins@autotest.powerdns.com built 20150610125050 mockbuild@)". 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 2008071869 · primary dns1.bondware.com

Found

Primary (MNAME)
dns1.bondware.com
Contact (RNAME)
noc.bondware.com
Serial
2008071869
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns1.bondware.com (52.5.104.98)2008071869
dns2.bondware.com (52.70.244.197)2008071869

Checks

  • ✓ Serial 2008071869 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.bondware.com is one of the listed nameservers.
  • ✓ Contact noc@bondware.com #25
    The SOA RNAME noc.bondware.com means noc@bondware.com.
  • ✓ Date-based serial #26
    The serial 2008071869 follows the YYYYMMDDnn convention (2008-07-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

9 records at the apex

Found

Read from
52.5.104.98:53
TypeValueTTL
SOAdns1.bondware.com. noc.bondware.com. 2008071869 10800 3600 1209600 8640086400
NSdns1.bondware.com.3600
NSdns2.bondware.com.3600
A18.211.141.2223600
MX10 mail.renderosity.com.3600
TXT"e2ma-verification=wyffb"3600
TXT"have-i-been-pwned-verification=717c70799299c81ae4defdcc1309a763"3600
TXT"google-site-verification=FBqlooh4iX9NtE-VF68cDdJmRIA0U-KvMeyhBd2Kb-0"3600
TXT"v=spf1 include:bondware.com include:e2ma.net include:amazonses.com ~all"300

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