bridalbus.com - robtex.com
bridalbus.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns5.afternic.com ⭐ | ||||||
| A | 2603:5:2134::42🇺🇸 GODADDY-DNS2603:5:2130::/44 | ||||||
| PTR | ns5.afternic.com | ||||||
| A | 97.74.99.66🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns5.afternic.com | ||||||
| NS | ns6.afternic.com | ||||||
| A | 2603:5:2234::42🇺🇸 GODADDY-DNS2603:5:2230::/44 | ||||||
| PTR | ns6.afternic.com | ||||||
| A | 173.201.67.66🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns6.afternic.com | ||||||
| NS | verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns5.afternic.comdns@jomax.net 2025-09-30 #0 | ||||||
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=1784259892 | ||||||
Same first word
bridalbus.com |
Similar names
DNS History
19 records (5 active, 14 former)
○NSns1.net4india.com2015-06-26 → 2016-04-20 · 4 obs
● 2016-04-20 16:14:32
○ 2016-12-29 05:27:48
○ 2026-07-17 03:55:24
○NSns13.domaincontrol.com2018-06-28 → 2026-05-24 · 5 obs
● 2018-06-28 05:55:08
● 2026-05-24 20:04:14
○ 2026-05-26 08:04:34
○ 2026-07-17 03:55:24
○NSns14.domaincontrol.com2018-06-28 → 2026-05-24 · 5 obs
● 2018-06-28 05:55:08
● 2026-05-24 20:04:14
○ 2026-05-26 08:04:34
○ 2026-07-17 03:55:24
○NSns2.net4india.com2015-06-26 → 2016-04-20 · 4 obs
● 2016-04-20 16:14:32
○ 2016-12-29 05:27:48
○ 2026-07-17 03:55:24
●NSns5.afternic.com2026-07-02 → 2026-07-17 · 3 obs
● 2026-07-02 12:59:44
● 2026-07-17 03:55:24
●NSns6.afternic.com2026-07-02 → 2026-07-17 · 3 obs
● 2026-07-02 12:59:44
● 2026-07-17 03:55:24
●NSverification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn2026-07-02 → 2026-07-17 · 3 obs
● 2026-07-02 12:59:44
● 2026-07-17 03:55:24
○MXalt1.aspmx.l.google.com2018-06-28 → 2018-06-28 · 3 obs
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
○MXalt2.aspmx.l.google.com2018-06-28 → 2018-06-28 · 3 obs
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
○MXaspmx.l.google.com2018-06-28 → 2018-06-28 · 3 obs
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
○MXaspmx2.googlemail.com2018-06-28 → 2018-06-28 · 3 obs
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
○MXaspmx3.googlemail.com2018-06-28 → 2018-06-28 · 3 obs
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
●A13.248.169.482026-07-02 → 2026-07-17 · 5 obs
● 2026-07-02 12:59:44
○ 2026-07-13 02:14:36
● 2026-07-13 09:21:32
● 2026-07-17 03:55:24
○A13.248.213.452026-05-06 → 2026-05-24 · 5 obs
● 2026-05-06 04:01:52
● 2026-05-24 20:04:14
○ 2026-05-26 08:04:34
○ 2026-07-17 03:55:24
○A162.159.140.1662026-05-06 → 2026-07-17 · 2 obs
○ 2026-07-17 03:55:24
○A192.64.83.202015-06-26 → 2016-04-20 · 4 obs
● 2016-04-20 16:14:32
○ 2016-12-29 05:27:48
○ 2026-07-17 03:55:24
○A199.34.228.432018-06-28 → 2018-06-28 · 4 obs
● 2018-06-28 05:55:08
○ 2026-05-06 04:01:52
○ 2026-07-17 03:55:24
●A76.223.54.1462026-07-02 → 2026-07-17 · 5 obs
● 2026-07-02 12:59:44
○ 2026-07-13 02:14:36
● 2026-07-13 09:21:32
● 2026-07-17 03:55:24
○A76.223.67.1892026-05-06 → 2026-05-24 · 5 obs
● 2026-05-06 04:01:52
● 2026-05-24 20:04:14
○ 2026-05-26 08:04:34
○ 2026-07-17 03:55:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bridalbus.com | ns5.afternic.com, ns6.afternic.com, verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn | 2 records |
✅ Authoritative Response
Server:97.74.99.66
NS records: ns5.afternic.com, ns6.afternic.com, verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bridalbus.com (unsigned zone)
⏱️ Timing
Total: 3245ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns5.afternic.com, ns6.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns5.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns5.afternic.com, ns6.afternic.com)
Analysis
IP Addresses
bridalbus.com has two IP addresses: 13.248.169.48 and 76.223.54.146
imagination-works.com, ember.org, choler.com plus two other host names have IP numbers in common with bridalbus.com.
Name Servers
bridalbus.com is served by three name servers: ns5.afternic.com, ns6.afternic.com and verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn.
There is at least partial name server overlap between bridalbus.com and other domains — www.taxibangkok.com, clorg.com, pathg.com and two more among them.
These name servers frequently co-occur with the name servers verification-gakbzzzqmt6gkcplw4efpp.ns101.verify.hn and verification-ex8vn3zniaperlcgbphvpy.ns101.verify.hn.
The hostnames ns5.afternic.com, ns6.afternic.com and verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn each direct to two IP addresses — ns5.afternic.com to 97.74.99.66 and 2603:5:2134::42, ns6.afternic.com to 173.201.67.66 and 2603:5:2234::42, and verification-mzprlrig7efh9fkwefm8sh.ns101.verify.hn to 13.248.169.48 and 76.223.54.146.