realgm.com

Checked 22 October 2026, 10:25 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2027-07-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
21 July 2000
Last changed
25 January 2026
Expires
21 July 2027
Status
client transfer prohibited, client update prohibited
Registry nameservers
ns1.epicworks.com, ns2.epicworks.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-07-21 #3
    The registration is valid until 2027-07-21 (272 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.epicworks.com, ns2.epicworks.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.epicworks.com, ns2.epicworks.com
NS in the zone
ns1.epicworks.com, ns2.epicworks.com
NameserverAddressesNetwork (AS)Glue
ns1.epicworks.com66.179.11.201AS1100 NUDAY - Nuday Networks Inc., CA66.179.11.201
ns2.epicworks.com5.78.154.236 2a01:4ff:1f0:c539::1AS212317 HETZNER-CLOUD3-AS - Hetzner Online GmbH, DE AS212317 HETZNER-CLOUD3-AS - Hetzner Online GmbH, DE2a01:4ff:1f0:c539::1 5.78.154.236

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.epicworks.com, ns2.epicworks.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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1100 (NUDAY - Nuday Networks Inc., CA): 1 address; AS212317 (HETZNER-CLOUD3-AS - Hetzner Online GmbH, DE): 2 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.epicworks.com.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.epicworks.com 66.179.11.201NOERROR, 94 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns2.epicworks.com 5.78.154.236NOERROR, 163 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17
ns2.epicworks.com 2a01:4ff:1f0:c539::1NOERROR, 170 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.epicworks.com: "9.20.29-1~deb13u1-Debian"; ns2.epicworks.com: "PowerDNS Authoritative Server 4.9.17". 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

info

serial 2026081503 · primary ns0.epicworks.com

Found

Primary (MNAME)
ns0.epicworks.com
Contact (RNAME)
hostmaster.epicworks.com
Serial
2026081503
Refresh / retry
1200 s / 900 s
Expire
1209600 s
Negative TTL
1200 s

Serial per nameserver

NameserverSerial
ns1.epicworks.com (66.179.11.201)2026081503
ns2.epicworks.com (5.78.154.236)2026081503
ns2.epicworks.com (2a01:4ff:1f0:c539::1)2026081503

Checks

  • ✓ Serial 2026081503 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 20m, retry 15m, expire 14d, negative TTL 20m.
  • i
    Hidden master (not resolvable)
    The primary nameserver ns0.epicworks.com is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact hostmaster@epicworks.com #25
    The SOA RNAME hostmaster.epicworks.com means hostmaster@epicworks.com.
  • ✓ Date-based serial #26
    The serial 2026081503 follows the YYYYMMDDnn convention (2026-08-15).

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

13 records at the apex

Found

Read from
66.179.11.201:53
TypeValueTTL
SOAns0.epicworks.com. hostmaster.epicworks.com. 2026081503 1200 900 1209600 12003600
NSns1.epicworks.com.3600
NSns2.epicworks.com.3600
A66.179.11.1973600
MX10 suede.epicworks.com.3600
TXT"google-site-verification=-vt1mIajnrbqtKDtgo6Vf-zaiHatl4mNnZH95e3NbcY"3600
TXT"MS=ms23643647"3600
TXT"v=spf1 ip4:66.179.11.192/27 ip4:64.185.229.0/24 include:spfa.mailendo.com ip4:209.167.115.0/24 ip4:66.48.77.192/26 -all"3600
CAA0 issue "digicert.com"3600
CAA0 iodef "mailto:abuse@epicworks.com"3600
CAA0 issue "pik.goog"3600
CAA0 issue "amazon.com"3600
CAA0 issue "letsencrypt.org"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.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, pik.goog, amazon.com, letsencrypt.org.