bridaltweet.com - robtex.com
bridaltweet.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=1774547832 | ||||||
Subdomains
www.bridaltweet.com |
Same first word
bridaltweet.com.ph |
bridaltweet.com |
DNS History
7 records (5 active, 2 former)
●NSns53.domaincontrol.com2015-06-20 → 2026-03-26 · 2 obs
● 2026-03-26 18:01:36
●NSns54.domaincontrol.com2015-06-20 → 2026-03-26 · 2 obs
● 2026-03-26 18:01:36
●MXbridaltweet-com.mail.protection.outlook.com2026-03-11 → 2026-03-26 · 3 obs
● 2026-03-11 09:04:40
● 2026-03-26 18:01:36
○MXmailstore1.secureserver.net2015-06-20 → 2016-12-30 · 4 obs
● 2016-12-30 23:06:40
○ 2026-03-11 09:04:40
○ 2026-03-26 18:01:36
○MXsmtp.secureserver.net2015-06-20 → 2016-12-30 · 4 obs
● 2016-12-30 23:06:40
○ 2026-03-11 09:04:40
○ 2026-03-26 18:01:36
●A208.82.16.682015-06-20 → 2026-03-26 · 2 obs
● 2026-03-26 18:01:36
●A2620:46:2000:16::682026-03-11 → 2026-03-26 · 3 obs
● 2026-03-11 09:04:40
● 2026-03-26 18:01:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bridaltweet.com | ns53.domaincontrol.com, ns54.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.74.27
NS records: ns53.domaincontrol.com, ns54.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bridaltweet.com (unsigned zone)
⏱️ Timing
Total: 2192ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.82.16.68 |
| AAAA | 1 | 2620:46:2000:16::68 |
| NS | 2 | ns53.domaincontrol.com, ns54.domaincontrol.com |
| MX | 1 | bridaltweet-com.mail.protection.outlook. |
| TXT | 4 | google-site-verification=H1-h5xjNlFOSHLk, NETORG5968994.onmicrosoft.com... |
| SOA | 1 | ns53.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns53.domaincontrol.com, ns53.domaincontrol.com, ns54.domaincontrol.com...)
Analysis
Hierarchy
bridaltweet.com is the parent of www.bridaltweet.com.
IP Addresses
The entity bridaltweet.com points to two IP numbers: 2620:46:2000:16::68 and 208.82.16.68.
For instance, other host names jimturnersmm.ning.com, cashis.ning.com, hairbangersradio.ning.com, s0rgullazax0.ning.com and plwg.net share IP numbers with bridaltweet.com.
Name Servers
bridaltweet.com is delegated to two name servers: ns53.domaincontrol.com and ns54.domaincontrol.com.
bridaltweet.com uses the same name server setup as other domains such as your-anchor.com, yorkkia.com, cancerintel.com, dp-architect.com and neweyeglasses.com.
bridaltweet.com shares name servers with other domains at least partially, for example infinitygroupuae.com.
Host names with two IP numbers:
ns53.domaincontrol.com points to 2603:5:21a2::1b and 97.74.106.27; ns54.domaincontrol.com points to 2603:5:22a2::1b and 173.201.74.27.
Mail Servers
bridaltweet.com is handled by a single mail server, bridaltweet-com.mail.protection.outlook.com.
Host name bridaltweet-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c901::1, 2a01:111:f403:c902::16, 2a01:111:f403:c946::5, 2a01:111:f403:f913::, 52.101.9.21, 52.101.10.1, 52.101.41.3 and 52.101.194.15.