magentocommerce.com

Checked 22 October 2026, 09:42 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 3 info

Registration

info

.com generic · Nom-iq Ltd. dba COM LAUDE · expires 2027-03-20

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Nom-iq Ltd. dba COM LAUDE
Registered
20 March 2007
Last changed
18 February 2026
Expires
20 March 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.magento.com, ns1.magentocommerce.com, ns2.magento.com, ns2.magentocommerce.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-20 #3
    The registration is valid until 2027-03-20 (148 days).
  • ✓ Transfer locked #4
    Registry status: client delete 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.magento.com, ns1.magentocommerce.com, ns2.magento.com, ns2.magentocommerce.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.magento.com, ns1.magentocommerce.com, ns2.magento.com, ns2.magentocommerce.com
NS in the zone
ns1.magento.com, ns1.magentocommerce.com, ns2.magento.com, ns2.magentocommerce.com
NameserverAddressesNetwork (AS)Glue
ns1.magento.com205.251.197.8AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.197.8
ns1.magentocommerce.com205.251.193.124AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.193.124
ns2.magento.com205.251.194.140AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.194.140
ns2.magentocommerce.com205.251.198.197AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.198.197

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.magento.com, ns1.magentocommerce.com, ns2.magento.com, ns2.magentocommerce.com.
  • ✓ 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: ns1.magentocommerce.com, ns2.magentocommerce.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 4 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 4 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.magento.com 205.251.197.8NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.magentocommerce.com 205.251.193.124NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.magento.com 205.251.194.140NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.magentocommerce.com 205.251.198.197NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 1 · primary ns1.magento.com

Found

Primary (MNAME)
ns1.magento.com
Contact (RNAME)
hostmaster.magento.com
Serial
1
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.magento.com (205.251.197.8)1
ns1.magentocommerce.com (205.251.193.124)1
ns2.magento.com (205.251.194.140)1
ns2.magentocommerce.com (205.251.198.197)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.magento.com is one of the listed nameservers.
  • ✓ Contact hostmaster@magento.com #25
    The SOA RNAME hostmaster.magento.com means hostmaster@magento.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

warn

16 records at the apex

Found

Read from
205.251.197.8:53
TypeValueTTL
SOAns1.magento.com. hostmaster.magento.com. 1 7200 900 1209600 60086400
NSns1.magento.com.86400
NSns1.magentocommerce.com.86400
NSns2.magento.com.86400
NSns2.magentocommerce.com.86400
A52.200.161.9160
A100.62.137.6860
A184.197.46.10460
A184.197.56.19360
TXT"9991a0e53c91417f8d3d7b7b0e19d155"3600
TXT"google-site-verification=bWB8FBdxMfxBS3xGsjeX_0NoYCw6D6IaEbY4-76VBAo"3600
TXT"v=spf1 ip4:195.14.125.1 include:mktomail.com include:sendgrid.net include:amazonses.com -all"3600
CAA0 iodef "mailto:magento-caa-reports@adobe.com"86400
CAA0 issue "amazon.com"86400
CAA0 issue "digicert.com"86400
CAA0 issuewild ";"86400

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: amazon.com, digicert.com, none (issuance forbidden).