stellarbride.com - dns.ninja
stellarbride.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix | ||||||
| PTR | ec2-13-56-33-8.us-west-1.compute.amazonaws.com | ||||||
| NS | ns1.brandbucket.com ⭐ | ||||||
| A | 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS | ||||||
| A | 54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix | ||||||
| PTR | ec2-54-241-53-41.us-west-1.compute.amazonaws.com | ||||||
| NS | ns2.brandbucket.com | ||||||
| A | 2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS | ||||||
| A | 18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix | ||||||
| PTR | ec2-18-221-52-246.us-east-2.compute.amazonaws.com | ||||||
| TXT | afternic-verification-cvgUQU8SkLxsjXcPBSk2CM | ||||||
| TXT | v=spf1 -all | ||||||
| TXT | 27aab5373841b85aab94982ee19ab62f96481ed6 | ||||||
| SOA | ns1.brandbucket.commail@stellarbride.com 2024-03-05 #2 | ||||||
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=1784416557 | ||||||
Same first word
stellarbride.com |
Similar names
DNS History
21 records (3 active, 18 former)
○NSdns1.stellarbride.com2017-12-22 → 2017-12-22 · 4 obs
○ 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○NSdns2.stellarbride.com2017-12-22 → 2017-12-22 · 4 obs
○ 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○NSns-cloud-a1.googledomains.com2016-04-24 → 2017-01-07 · 5 obs
○ 2015-10-23 19:06:58
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
○NSns-cloud-a2.googledomains.com2016-04-24 → 2017-01-07 · 5 obs
○ 2015-10-23 19:06:58
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
○NSns-cloud-a3.googledomains.com2016-04-24 → 2017-01-07 · 5 obs
○ 2015-10-23 19:06:58
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
○NSns-cloud-a4.googledomains.com2016-04-24 → 2017-01-07 · 5 obs
○ 2015-10-23 19:06:58
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
●NSns1.brandbucket.com2026-02-24 → 2026-07-18 · 3 obs
○ 2017-12-22 00:27:16
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
●NSns2.brandbucket.com2026-02-24 → 2026-07-18 · 3 obs
○ 2017-12-22 00:27:16
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
○NSns31.domaincontrol.com2015-06-01 → 2015-06-01 · 3 obs
● 2015-06-01 04:13:56
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○NSns32.domaincontrol.com2015-06-01 → 2015-06-01 · 3 obs
● 2015-06-01 04:13:56
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○MXalt1.aspmx.l.google.com2017-01-07 → 2017-12-22 · 5 obs
○ 2015-10-23 19:06:58
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○MXalt2.aspmx.l.google.com2017-01-07 → 2017-12-22 · 5 obs
○ 2015-10-23 19:06:58
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○MXalt3.aspmx.l.google.com2017-01-07 → 2017-12-22 · 5 obs
○ 2015-10-23 19:06:58
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○MXalt4.aspmx.l.google.com2017-01-07 → 2017-12-22 · 5 obs
○ 2015-10-23 19:06:58
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○MXaspmx.l.google.com2017-01-07 → 2017-12-22 · 5 obs
○ 2015-10-23 19:06:58
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
○MXmailstore1.secureserver.net2015-06-01 → 2015-06-01 · 3 obs
● 2015-06-01 04:13:56
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○MXsmtp.secureserver.net2015-06-01 → 2015-06-01 · 3 obs
● 2015-06-01 04:13:56
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○A104.197.183.982016-04-24 → 2017-01-07 · 5 obs
○ 2015-10-23 19:06:58
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
● 2016-04-24 15:49:12
● 2017-01-07 17:18:48
○ 2017-12-22 00:27:16
○ 2026-07-18 23:21:10
●A13.56.33.82026-02-24 → 2026-07-18 · 3 obs
○ 2017-12-22 00:27:16
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
● 2026-02-24 09:15:10
● 2026-07-18 23:21:10
○A184.168.221.742015-06-01 → 2015-06-01 · 3 obs
● 2015-06-01 04:13:56
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○ 2015-10-23 19:06:58
○ 2026-07-18 23:21:10
○A50.63.15.2172017-12-22 → 2017-12-22 · 4 obs
○ 2017-01-07 17:18:48
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
● 2017-12-22 00:27:16
○ 2026-02-24 09:15:10
○ 2026-07-18 23:21:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| stellarbride.com | ns1.brandbucket.com, ns2.brandbucket.com | 2 records |
✅ Authoritative Response
Server:54.241.53.41
NS records: ns1.brandbucket.com, ns2.brandbucket.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stellarbride.com (unsigned zone)
⏱️ Timing
Total: 304ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.56.33.8 |
| NS | 2 | ns2.brandbucket.com, ns1.brandbucket.com |
| TXT | 3 | afternic-verification-cvgUQU8SkLxsjXcPBS, 27aab5373841b85aab94982ee19ab62f96481ed6... |
| SOA | 1 | ns1.brandbucket.com mail.stellarbride.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)
Analysis
IP Addresses
stellarbride.com has exactly one IP address — 13.56.33.8.
quvo.com, precisionhuman.com, intellectial.com plus two other host names have IP numbers in common with stellarbride.com.
Name Servers
The NS records for stellarbride.com delegate to ns1.brandbucket.com and ns2.brandbucket.com.
The name server configuration of stellarbride.com is shared with other domains, for instance bestword.com, devreel.com, presentrate.com and two others.
ns1.brandbucket.com resolves to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361. Likewise, ns2.brandbucket.com resolves to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8 — two IP addresses apiece.