sumaclub.com - robtex.com
sumaclub.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1783470201 | ||||||
Same first word
sumaclub.com |
Similar names
DNS History
10 records (6 active, 4 former)
○NSns15.domaincontrol.com2016-04-24 → 2016-04-24 · 3 obs
○ 2017-01-19 10:55:10
○ 2026-07-08 00:30:04
○NSns16.domaincontrol.com2016-04-24 → 2016-04-24 · 3 obs
○ 2017-01-19 10:55:10
○ 2026-07-08 00:30:04
●NSpdns07.domaincontrol.com2017-01-19 → 2026-07-08 · 3 obs
● 2017-01-19 10:55:10
● 2026-07-08 00:30:04
●NSpdns08.domaincontrol.com2017-01-19 → 2026-07-08 · 3 obs
● 2017-01-19 10:55:10
● 2026-07-08 00:30:04
●NSpdns11.domaincontrol.com2020-04-05 → 2026-07-08 · 3 obs
● 2020-04-05 23:22:50
● 2026-07-08 00:30:04
●MXmailstore1.secureserver.net2016-04-24 → 2026-07-08 · 2 obs
● 2026-07-08 00:30:04
●MXsmtp.secureserver.net2016-04-24 → 2026-07-08 · 2 obs
● 2026-07-08 00:30:04
○A132.148.1.2372017-01-19 → 2017-01-19 · 4 obs
● 2017-01-19 10:55:10
○ 2020-04-05 23:22:50
○ 2026-07-08 00:30:04
●A166.62.101.802020-04-05 → 2026-07-08 · 3 obs
● 2020-04-05 23:22:50
● 2026-07-08 00:30:04
○A50.63.202.632016-04-24 → 2016-04-24 · 3 obs
○ 2017-01-19 10:55:10
○ 2026-07-08 00:30:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| sumaclub.com | pdns07.domaincontrol.com, pdns08.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.111.53
NS records: pdns07.domaincontrol.com, pdns08.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sumaclub.com (unsigned zone)
⏱️ Timing
Total: 130ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 166.62.101.80 |
| NS | 2 | pdns07.domaincontrol.com, pdns08.domaincontrol.com |
| MX | 2 | mailstore1.secureserver.net (pri: 10), smtp.secureserver.net (pri: 0) |
| TXT | 1 | google-site-verification=xSr6zJxdvNOoLan |
| SOA | 1 | pdns11.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (pdns07.domaincontrol.com, pdns07.domaincontrol.com, pdns08.domaincontrol.com...)
Analysis
IP Addresses
sumaclub.com resolves to one IP address: 166.62.101.80.
80.101.62.166.host.secureserver.net is an example of another host name that shares IP numbers with sumaclub.com.
Name Servers
sumaclub.com has three name servers — pdns07.domaincontrol.com, pdns08.domaincontrol.com and pdns11.domaincontrol.com.
There is at least partial name server overlap between sumaclub.com and other domains — meride.tv, amisgest.org, dakotadiscovery.org and two more among them.
These name servers are routinely deployed together with the name servers pdns12.domaincontrol.com.
Each of pdns07.domaincontrol.com, pdns08.domaincontrol.com and pdns11.domaincontrol.com points to two IP numbers. pdns07.domaincontrol.com points to 97.74.111.53 and 2603:5:21f1::35. pdns08.domaincontrol.com points to 173.201.79.53 and 2603:5:22f1::35. pdns11.domaincontrol.com points to 97.74.111.55 and 2603:5:21f2::37.
Mail Servers
Mail for sumaclub.com is handled by two mail servers — mailstore1.secureserver.net and smtp.secureserver.net.
sumaclub.com uses an identical mail server configuration to several other domains — among them cantgointhere.com, iloansmart.com, ladychellez.com and two more.
Some mail servers of sumaclub.com are also used by other domains, notably saactive.co.za and nallandvoid.com.
mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162. smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113. Both hosts resolve to three IP numbers.