stack.how - robtex.com
stack.how
how
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
12 records (7 active, 5 former)
●NSdns1.registrar-servers.com2026-02-20 → 2026-07-11 · 3 obs
● 2026-02-20 14:56:22
● 2026-07-11 08:45:28
●NSdns2.registrar-servers.com2026-02-20 → 2026-07-11 · 3 obs
● 2026-02-20 14:56:22
● 2026-07-11 08:45:28
○NSns1psw.name.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-02-20 14:56:22
○ 2026-07-11 08:45:28
○NSns2nsw.name.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-02-20 14:56:22
○ 2026-07-11 08:45:28
○NSns3cpr.name.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-02-20 14:56:22
○ 2026-07-11 08:45:28
○NSns4lpv.name.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-02-20 14:56:22
○ 2026-07-11 08:45:28
●MXalt1.aspmx.l.google.com2026-02-20 → 2026-07-11 · 2 obs
● 2026-07-11 08:45:28
●MXalt2.aspmx.l.google.com2026-02-20 → 2026-07-11 · 2 obs
● 2026-07-11 08:45:28
●MXaspmx.l.google.com2026-02-20 → 2026-07-11 · 2 obs
● 2026-07-11 08:45:28
●MXaspmx2.googlemail.com2026-02-20 → 2026-07-11 · 2 obs
● 2026-07-11 08:45:28
●MXaspmx3.googlemail.com2026-02-20 → 2026-07-11 · 2 obs
● 2026-07-11 08:45:28
○A69.64.147.2422017-11-03 → 2017-11-03 · 3 obs
○ 2026-02-20 14:56:22
○ 2026-07-11 08:45:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| stack.how | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stack.how (unsigned zone)
⏱️ Timing
Total: 1432ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=Nt1GdS0tOCfAIV5 |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
stack.how uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
stack.how has the same name server delegation as a number of other domains, such as 3darchitect.net, inmersa.net, pontadelgadahotels.com and two more.
Some of stack.how's name servers are also used by other domains, including lunasee.net, protectvision.net, slmbz.com and alucodev.com.
These name servers regularly co-occur with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
stack.how is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
stack.how shares at least some of its mail servers with other domains — for example edion.jp, aviatoragent.com, pagetronics.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 64.233.180.26 and 2607:f8b0:4004:c07::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.