podchief.com - robtex.com
podchief.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=1771291435 | ||||||
Same first word
podchief.com |
DNS History
13 records (8 active, 5 former)
●NSdns1.registrar-servers.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
●NSdns2.registrar-servers.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
○NSns45.domaincontrol.com2015-11-02 → 2017-01-25 · 4 obs
● 2017-01-25 10:07:48
○ 2019-02-13 13:11:28
○ 2026-03-24 04:39:44
○NSns46.domaincontrol.com2015-11-02 → 2017-01-25 · 4 obs
● 2017-01-25 10:07:48
○ 2019-02-13 13:11:28
○ 2026-03-24 04:39:44
●MXalt1.aspmx.l.google.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
●MXalt2.aspmx.l.google.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
●MXalt3.aspmx.l.google.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
●MXalt4.aspmx.l.google.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
●MXaspmx.l.google.com2026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
○MXmailstore1.secureserver.net2015-11-02 → 2017-01-25 · 4 obs
● 2017-01-25 10:07:48
○ 2019-02-13 13:11:28
○ 2026-03-24 04:39:44
○MXsmtp.secureserver.net2015-11-02 → 2017-01-25 · 4 obs
● 2017-01-25 10:07:48
○ 2019-02-13 13:11:28
○ 2026-03-24 04:39:44
●A18.135.164.22026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 04:39:44
○A184.168.221.622015-11-02 → 2017-01-25 · 4 obs
● 2017-01-25 10:07:48
○ 2019-02-13 13:11:28
○ 2026-03-24 04:39:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, a.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| podchief.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for podchief.com (unsigned zone)
⏱️ Timing
Total: 409ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 18.135.164.2 |
| 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)... |
| 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
IP Addresses
podchief.com resolves to one IP number: 18.135.164.2.
Other host names, for instance podlinked.com, www.beep2b.com, linkedsavvy.com, ec2-18-135-164-2.eu-west-2.compute.amazonaws.com and beep.academy share IP numbers with podchief.com.
Name Servers
podchief.com's delegation uses two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
podchief.com uses the same name server setup as other domains, such as songbat.com, proga.com, ristotle.com, khroom-sport.com and us02www-zoom.us.
podchief.com at least partially shares name servers with other domains, for instance leventkirca.website, maxclark.info, sheminlaw.com and thermalboundaries.com.
These name servers are commonly used with dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
Host names with two IPs:
dns1.registrar-servers.com points to 2610:a1:1024::200 and 156.154.132.200
dns2.registrar-servers.com points to 2610:a1:1025::200 and 156.154.133.200
Mail Servers
podchief.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
podchief.com shares at least some mail servers with other domains, for example ns500699.ns500765.ns500699.ns500734.ns500734.ns500693.ns500588.ns500683.ns500683.ns500612.ns500612.ns500110.dtrkdll.com, hotelgeerts.be, ns500759.ns500758.ns500758.ns500698.ns500736.ns500698.ns500736.ns500708.ns500619.ns500686.ns500576.ns500652.ns500576.trackreceptor.com, ns500698.ns500758.ns500736.ns500698.ns500736.ns500698.ns500735.ns500698.ns500735.ns500698.ns500708.ns500708.ns500686.ns500619.ns500576.trackreceptor.com and ns500731.ns500742.ns500731.ns500742.ns500731.ns500688.ns500671.ns500678.ns500671.ns500705.ns500291.ns500291.ns500649.ns500291.ns500666.tenderladiesbz.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27.