teracode.com - dns.ninja
teracode.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=1786755024 | ||||||
Subdomains
Same first word
Similar names
DNS History
13 records (8 active, 5 former)
●NSns63.domaincontrol.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●NSns64.domaincontrol.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●MXalt1.aspmx.l.google.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●MXalt2.aspmx.l.google.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●MXaspmx.l.google.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●MXaspmx2.googlemail.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
●MXaspmx3.googlemail.com2015-07-15 → 2026-08-15 · 2 obs
● 2026-08-15 01:16:42
○A198.185.159.1442018-08-19 → 2018-08-19 · 4 obs
● 2018-08-19 20:45:00
○ 2026-02-16 20:52:02
○ 2026-08-15 01:16:42
○A198.185.159.1452018-08-19 → 2018-08-19 · 4 obs
● 2018-08-19 20:45:00
○ 2026-02-16 20:52:02
○ 2026-08-15 01:16:42
○A198.49.23.1442018-08-19 → 2018-08-19 · 4 obs
● 2018-08-19 20:45:00
○ 2026-02-16 20:52:02
○ 2026-08-15 01:16:42
○A198.49.23.1452018-08-19 → 2018-08-19 · 4 obs
● 2018-08-19 20:45:00
○ 2026-02-16 20:52:02
○ 2026-08-15 01:16:42
○A54.225.76.172015-07-15 → 2016-11-05 · 4 obs
● 2016-11-05 18:45:50
○ 2018-08-19 20:45:00
○ 2026-08-15 01:16:42
●A92.205.6.62026-02-16 → 2026-08-15 · 3 obs
● 2026-02-16 20:52:02
● 2026-08-15 01:16:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net... | - |
| teracode.com | ns63.domaincontrol.com, ns64.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.42
NS records: ns63.domaincontrol.com, ns64.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for teracode.com (unsigned zone)
⏱️ Timing
Total: 388ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 92.205.6.6 |
| NS | 2 | ns63.domaincontrol.com, ns64.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 8 | linkedin-site-verification=cbb602cf-af84, MS=74C8FED0FB983A7CD96E98A0C1B015972538E... |
| SOA | 1 | ns63.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns63.domaincontrol.com, ns63.domaincontrol.com, ns64.domaincontrol.com...)
Analysis
Hierarchy
teracode.com serves as the parent of imap.teracode.com, aws1.teracode.com, devel.teracode.com and files.teracode.com.
IP Addresses
teracode.com resolves to one IP address: 92.205.6.6.
sxb1plzcpnl459831.prod.sxb1.secureserver.net, mail.rvh.org.uk, wasserwerte.de and two other host names share IP numbers with teracode.com.
Name Servers
Two name servers handle the delegation for teracode.com: ns63.domaincontrol.com and ns64.domaincontrol.com.
teracode.com uses the same name servers as several other domains — among them l2create.com, medliensearch.com, minneapolischronicle.com and two more.
ns63.domaincontrol.com and ns64.domaincontrol.com both carry two IP addresses. The A records for ns63.domaincontrol.com are 97.74.101.42 and 2603:5:2154::2a; the A records for ns64.domaincontrol.com are 173.201.69.42 and 2603:5:2254::2a.
Mail Servers
teracode.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
teracode.com has at least partial mail server overlap with other domains such as loba.com, arabianpetroleum.co.in.cdn.cloudflare.net, ns500759.ns500759.ns500758.ns500698.ns500735.ns500736.ns500698.ns500698.ns500735.ns500708.ns500576.ns500619.ns500576.ns500576.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.
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: 142.251.111.27 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1b IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1a IP addresses.