topsitenet.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-03-01

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
9 January 2003
Last changed
2 March 2026
Expires
1 March 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.interfuse1.com, ns2.interfuse1.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-03-01 #3
    The registration is valid until 2027-03-01 (130 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

ns1.interfuse1.com, ns2.interfuse1.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.interfuse1.com, ns2.interfuse1.com
NS in the zone
ns1.interfuse1.com, ns2.interfuse1.com
NameserverAddressesNetwork (AS)Glue
ns1.interfuse1.com69.16.238.138AS32244 LIQUIDWEB - Liquid Web, L.L.C, US69.16.238.138
ns2.interfuse1.com69.16.238.204AS32244 LIQUIDWEB - Liquid Web, L.L.C, US69.16.238.138

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.interfuse1.com, ns2.interfuse1.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns2.interfuse1.com (glue 69.16.238.138, zone 69.16.238.204). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 69.16.238.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 (AS32244 (LIQUIDWEB - Liquid Web, L.L.C, US): 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 .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
ns1.interfuse1.com 69.16.238.138NOERROR, 105 ms, authoritativenoyes / yesrefused9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16
ns2.interfuse1.com 69.16.238.204NOERROR, 107 ms, authoritativenoyes / yesrefused9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16

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: ns1.interfuse1.com: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16"; ns2.interfuse1.com: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16". 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 2026100700 · primary ns1.interfuse1.com

Found

Primary (MNAME)
ns1.interfuse1.com
Contact (RNAME)
nniesen.tds.net
Serial
2026100700
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.interfuse1.com (69.16.238.138)2026100700
ns2.interfuse1.com (69.16.238.204)2026100700

Checks

  • ✓ Serial 2026100700 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.interfuse1.com is one of the listed nameservers.
  • ✓ Contact nniesen@tds.net #25
    The SOA RNAME nniesen.tds.net means nniesen@tds.net.
  • ✓ Date-based serial #26
    The serial 2026100700 follows the YYYYMMDDnn convention (2026-10-07).

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

7 records at the apex

Found

Read from
69.16.238.138:53
TypeValueTTL
SOAns1.interfuse1.com. nniesen.tds.net. 2026100700 86400 7200 3600000 8640086400
NSns2.interfuse1.com.86400
NSns1.interfuse1.com.86400
A69.16.238.138300
MX0 topsitenet.com.300
TXT"v=spf1 ip4:69.16.238.138 +a +mx +ip4:69.16.238.33 ~all"300
TXT"google-site-verification=_dXhlwulTyKgRG3mPK0ZUHSoadLSdOo2KxOakFlgY5Q"300

Checks

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