bridesavvy.com - robtex.com
bridesavvy.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=1778434076 | ||||||
Same first word
bridesavvy.com |
DNS History
10 records (10 active, 0 former)
●NSns-cloud-c1.googledomains.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●NSns-cloud-c2.googledomains.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●NSns-cloud-c3.googledomains.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●NSns-cloud-c4.googledomains.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●MXalt1.aspmx.l.google.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●MXalt2.aspmx.l.google.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●MXalt3.aspmx.l.google.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●MXalt4.aspmx.l.google.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●MXaspmx.l.google.com2016-11-28 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
●A75.101.134.272026-04-05 → 2026-05-10 · 2 obs
● 2026-05-10 17:43:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bridesavvy.com | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.108
NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bridesavvy.com (unsigned zone)
⏱️ Timing
Total: 375ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.101.134.27 |
| NS | 4 | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)
Analysis
IP Addresses
bridesavvy.com points to a single IP: 75.101.134.27.
Other host names, for instance carpetbarn.net, dennytesta.com, mail.michellelarmandphotography.com, mail.themotherofallbabyshowers.com and tammychristina.com share IP numbers with bridesavvy.com.
Name Servers
bridesavvy.com's delegation is handled by four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
bridesavvy.com partially shares name servers with other domains; examples include apollo.clinic, hydeparkmedicalclinic.com.au, gulfce.com, nonutnation.com and highdesertdispatch.com.
Host names with two IPs:
ns-cloud-c1.googledomains.com points to 2001:4860:4802:32::6c and 216.239.32.108
ns-cloud-c2.googledomains.com points to 2001:4860:4802:34::6c and 216.239.34.108
ns-cloud-c3.googledomains.com points to 2001:4860:4802:36::6c and 216.239.36.108
ns-cloud-c4.googledomains.com points to 2001:4860:4802:38::6c and 216.239.38.108
Mail Servers
Five mail servers handle bridesavvy.com: 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.
bridesavvy.com shares some mail servers with other domains, at least partially, such as ns500754.ns500671.ns500742.ns500704.ns500671.ns500704.ns500671.ns500649.ns500678.ns500291.ns500671.ns500666.ns500153.tenderladiesbz.com, ns500671.ns500742.ns500742.ns500731.ns500731.ns500742.ns500742.ns500671.ns500705.ns500671.ns500688.ns500291.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500693.ns500693.ns500699.ns500693.ns500699.ns500693.ns500588.ns500693.ns500588.ns500693.ns500683.ns500588.dtrkdll.com, ns500758.ns500759.ns500759.ns500735.ns500698.ns500735.ns500735.ns500735.ns500736.ns500576.ns500576.ns500619.ns500652.trackreceptor.com and ns500737.ns500599.ns500599.ns500599.ns500737.ns500737.ns500583.ns500697.www.yummyflingsfinder.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: 2a00:1450:4009:c19::1a and 192.178.223.27
alt1.aspmx.l.google.com points to: 2800:3f0:4003:c0f::1a and 108.177.123.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4023:3003::1a and 172.253.145.27
alt3.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1b and 172.253.135.26
alt4.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.27