tegraco.com - dns.ninja
tegraco.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=1786814079 | ||||||
Same first word
tegraco.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns65.domaincontrol.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●NSns66.domaincontrol.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●MXalt1.aspmx.l.google.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●MXalt2.aspmx.l.google.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●MXaspmx.l.google.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●MXaspmx2.googlemail.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●MXaspmx3.googlemail.com2016-12-17 → 2026-08-15 · 2 obs
● 2026-08-15 17:41:52
●A151.101.194.1592026-02-26 → 2026-08-15 · 3 obs
● 2026-02-26 05:26:26
● 2026-08-15 17:41:52
○A192.124.249.622016-12-17 → 2017-08-16 · 4 obs
● 2017-08-16 10:44:10
○ 2026-02-26 05:26:26
○ 2026-08-15 17:41:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| tegraco.com | ns66.domaincontrol.com, ns65.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.70.43
NS records: ns66.domaincontrol.com, ns65.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tegraco.com (unsigned zone)
⏱️ Timing
Total: 1243ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 151.101.194.159 |
| NS | 2 | ns65.domaincontrol.com, ns66.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=GzYwiiZ43sgjamQ, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns65.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)
Analysis
IP Addresses
tegraco.com resolves to just one IP address, 151.101.194.159.
Name Servers
Two name servers handle the delegation for tegraco.com: ns65.domaincontrol.com and ns66.domaincontrol.com.
ns65.domaincontrol.com and ns66.domaincontrol.com both carry two IP addresses. The A records for ns65.domaincontrol.com are 97.74.102.43 and 2603:5:2164::2b; the A records for ns66.domaincontrol.com are 173.201.70.43 and 2603:5:2264::2b.
Mail Servers
Five mail servers handle tegraco.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
Host names that have two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to two addresses: 192.178.155.27 and 2607:f8b0:4004:c19::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1a IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 192.178.234.27 IP addresses.