stackbuffer.in - dns.ninja
stackbuffer.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1787408462 | ||||||
Same first word
stackbuffer.in |
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns33.domaincontrol.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●NSns34.domaincontrol.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●MXalt1.aspmx.l.google.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●MXalt2.aspmx.l.google.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●MXalt3.aspmx.l.google.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●MXalt4.aspmx.l.google.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●MXaspmx.l.google.com2026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
●A199.36.158.1002026-08-18 → 2026-08-22 · 2 obs
● 2026-08-22 15:06:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns2.registry.in, ns3.registry.in, ns4.registry.in, ns1.registry.in | - |
| stackbuffer.in | ns33.domaincontrol.com, ns34.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.74.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stackbuffer.in (unsigned zone)
⏱️ Timing
Total: 744ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.36.158.100 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 3 | hosting-site=sb-ai-website-prod, MS=501C4EE65A6302454B768937CD9F5D3754390... |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
stackbuffer.in resolves to just one IP address, 199.36.158.100.
Two other host names, along with dentalxray.org, playclass.com.co and meta-business-case-38e40.web.app, also share IP numbers with stackbuffer.in.
Name Servers
The NS records for stackbuffer.in delegate to ns33.domaincontrol.com and ns34.domaincontrol.com.
stackbuffer.in shares its NS records with other domains, for example recordhuman.com, irsrescuesquad.com, bourbongunsandroses.com and two others.
stackbuffer.in and other domains like doctorinsta.com share at least a portion of their name servers.
ns33.domaincontrol.com resolves to 97.74.106.17 and 2603:5:21a1::11. Likewise, ns34.domaincontrol.com resolves to 173.201.74.17 and 2603:5:22a1::11 — two IP addresses apiece.
Mail Servers
stackbuffer.in has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between stackbuffer.in and other domains, including cardboardgamer.com.au, opso.co, bonbet.ca and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
The A records for aspmx.l.google.com return 64.233.180.26 and 2607:f8b0:4004:c21::1a.
The A records for alt1.aspmx.l.google.com return 192.178.234.26 and 2800:3f0:4003:c14::1b.
The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.
The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1a.