bingchef.com - robtex.com
bingchef.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=1784971362 | ||||||
Same first word
bingchef.com |
DNS History
15 records (12 active, 3 former)
●NSns-1324.awsdns-37.org2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●NSns-1577.awsdns-05.co.uk2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●NSns-507.awsdns-63.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●NSns-732.awsdns-27.net2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXalt1.aspmx.l.google.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXalt2.aspmx.l.google.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXaspmx.l.google.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXaspmx2.googlemail.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXaspmx3.googlemail.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXaspmx4.googlemail.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
●MXaspmx5.googlemail.com2015-07-20 → 2026-07-25 · 2 obs
● 2026-07-25 09:36:58
○A119.81.26.342015-07-20 → 2015-07-20 · 3 obs
○ 2026-03-24 03:12:24
○ 2026-07-25 09:36:58
○A174.36.228.1302015-07-20 → 2016-04-07 · 4 obs
● 2016-04-07 18:11:56
○ 2026-03-24 03:12:24
○ 2026-07-25 09:36:58
●A45.79.163.1582026-03-24 → 2026-07-25 · 3 obs
● 2026-03-24 03:12:24
● 2026-07-25 09:36:58
○A50.97.219.342015-07-20 → 2015-07-20 · 3 obs
○ 2026-03-24 03:12:24
○ 2026-07-25 09:36:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bingchef.com | ns-732.awsdns-27.net, ns-507.awsdns-63.com, ns-1577.awsdns-05.co.uk, ns-1324.awsdns-37.org | 2 records |
✅ Authoritative Response
Server:205.251.197.44
NS records: ns-732.awsdns-27.net, ns-507.awsdns-63.com, ns-1577.awsdns-05.co.uk, ns-1324.awsdns-37.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bingchef.com (unsigned zone)
⏱️ Timing
Total: 471ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.79.163.158 |
| NS | 4 | ns-1324.awsdns-37.org, ns-1577.awsdns-05.co.uk... |
| MX | 7 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| SOA | 1 | ns-1324.awsdns-37.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-507.awsdns-63.com, ns-507.awsdns-63.com)
Analysis
IP Addresses
bingchef.com has exactly one IP address — 45.79.163.158.
Name Servers
Four name servers handle the delegation for bingchef.com: ns-507.awsdns-63.com, ns-732.awsdns-27.net, ns-1324.awsdns-37.org and ns-1577.awsdns-05.co.uk.
bingchef.com has at least partial name server overlap with other domains, such as 64-127.148.103.92.in-addr.arpa, sgc.rs, hornybeast.net and two others.
ns-507.awsdns-63.com, ns-732.awsdns-27.net, ns-1324.awsdns-37.org and ns-1577.awsdns-05.co.uk all point to exactly two IP numbers each: ns-507.awsdns-63.com → 205.251.193.251 and 2600:9000:5301:fb00::1; ns-732.awsdns-27.net → 205.251.194.220 and 2600:9000:5302:dc00::1; ns-1324.awsdns-37.org → 205.251.197.44 and 2600:9000:5305:2c00::1; ns-1577.awsdns-05.co.uk → 205.251.198.41 and 2600:9000:5306:2900::1.
Mail Servers
Mail for bingchef.com is routed through 7 mail servers, including aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
At least some of the mail servers used by bingchef.com are shared with other domains: ns500731.ns500742.ns500671.ns500731.ns500688.ns500704.ns500671.ns500678.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500698.ns500759.ns500759.ns500698.ns500735.ns500698.ns500698.ns500698.ns500736.ns500619.ns500698.ns500652.ns500576.trackreceptor.com, ns500724.ns500737.ns500724.ns500599.ns500724.ns500737.ns500737.ns500583.ns500697.ns500583.ns500669.www.yummyflingsfinder.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx4.googlemail.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
aspmx5.googlemail.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.
aspmx.l.google.com resolves to 142.250.141.26 and 2607:f8b0:4023:c0b::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.145.26 and 2607:f8b0:4023:3003::1b.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1a IP addresses.