techcardtcs.com - dns.ninja
techcardtcs.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=1783090271 | ||||||
Same first word
techcardtcs.com |
DNS History
10 records (10 active, 0 former)
●NSdns1.registrar-servers.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●NSdns2.registrar-servers.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●NSdns3.registrar-servers.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●NSdns4.registrar-servers.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●NSdns5.registrar-servers.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●MXalt1.aspmx.l.google.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●MXalt2.aspmx.l.google.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●MXaspmx.l.google.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●MXaspmx2.googlemail.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
●MXaspmx3.googlemail.com2016-12-15 → 2026-07-03 · 2 obs
● 2026-07-03 15:19:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net... | - |
| techcardtcs.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ 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 techcardtcs.com (unsigned zone)
⏱️ Timing
Total: 193ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 5 | dns1.registrar-servers.com, dns2.registrar-servers.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:spf.privateemail.com ~all, google-site-verification=ZYDSX_NunzaiGj3 |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
techcardtcs.com delegates to five name servers: dns1.registrar-servers.com, dns2.registrar-servers.com, dns3.registrar-servers.com and two others.
techcardtcs.com has at least partial name server overlap with other domains, such as yttik.com, losjefesgrill.com, arpanmpatel.com and two others.
It is common to see these name servers used together with name servers dns4.registrar-servers.com and dns5.registrar-servers.com.
Host names that have two IP addresses:
dns1.registrar-servers.com directs traffic to 156.154.132.200 and 2610:a1:1024::200.
dns2.registrar-servers.com directs traffic to 156.154.133.200 and 2610:a1:1025::200.
Host names that point to one IP address:
dns3.registrar-servers.com has the IP address 156.154.132.200.
dns4.registrar-servers.com has the IP address 156.154.133.200.
dns5.registrar-servers.com has the IP address 156.154.132.200.
Each of dns1.registrar-servers.com, dns3.registrar-servers.com and dns5.registrar-servers.com resolves to 156.154.132.200.
Both dns2.registrar-servers.com and dns4.registrar-servers.com resolve to 156.154.133.200 IP addresses each.
Mail Servers
Mail for techcardtcs.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between techcardtcs.com and other domains, including webpixels.io, paddingtonmarkets.com.au, ns500758.ns500698.ns500698.ns500758.ns500698.ns500735.ns500698.ns500736.ns500698.ns500735.ns500576.ns500698.ns500698.ns500698.ns500619.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
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::1a IP addresses each.