internetlivestats.com

Checked 22 October 2026, 09:21 UTC · via 8.8.8.8
!Passed with warnings
22 passed 4 warnings 0 failed 5 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 2013
Last changed
12 October 2026
Expires
12 October 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.magicpeach.com, ns2.magicpeach.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 (354 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.magicpeach.com, ns2.magicpeach.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.magicpeach.com, ns2.magicpeach.com
NS in the zone
ns1.magicpeach.com, ns2.magicpeach.com
NameserverAddressesNetwork (AS)Glue
ns1.magicpeach.com170.249.202.146AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US170.249.202.146
ns2.magicpeach.com170.249.202.147AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US170.249.202.147

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.magicpeach.com, ns2.magicpeach.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 one network
    all IPv4 addresses are in 170.249.202.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 (AS63410 (PRIVATESYSTEMS - PrivateSystems Networks, 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.magicpeach.com 170.249.202.146NOERROR, 105 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 11:52:06 by root@bh-centos-7.dev.cpanel.net)
ns2.magicpeach.com 170.249.202.147NOERROR, 102 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 11:52:06 by root@bh-centos-7.dev.cpanel.net)

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.magicpeach.com: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 11:52:06 by root@bh-centos-7.dev.cpanel.net)"; ns2.magicpeach.com: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 11:52:06 by root@bh-centos-7.dev.cpanel.net)". 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 2026092101 · primary ns1.magicpeach.com

Found

Primary (MNAME)
ns1.magicpeach.com
Contact (RNAME)
info.dadax.com
Serial
2026092101
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.magicpeach.com (170.249.202.146)2026092101
ns2.magicpeach.com (170.249.202.147)2026092101

Checks

  • ✓ Serial 2026092101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.magicpeach.com is one of the listed nameservers.
  • ✓ Contact info@dadax.com #25
    The SOA RNAME info.dadax.com means info@dadax.com.
  • ✓ Date-based serial #26
    The serial 2026092101 follows the YYYYMMDDnn convention (2026-09-21).

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

6 records at the apex

Found

Read from
170.249.202.146:53
TypeValueTTL
SOAns1.magicpeach.com. info.dadax.com. 2026092101 3600 1800 1209600 8640086400
NSns1.magicpeach.com.86400
NSns2.magicpeach.com.86400
A170.249.202.14814400
MX10 mail.internetlivestats.com.14400
TXT"v=spf1 +a +mx +ip4:170.249.202.146 +ip4:170.249.202.148 -all"14400

Checks

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