brideaccess.com - robtex.com

brideaccess.com

DNSSEC⚠️ Not signed
A70.40.200.72🇺🇸 EIGI70.40.192.0/19 Unified Layer
PTR70-40-200-72.unifiedlayer.com
NSns1.bluehost.com ⭐
A162.159.24.80Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.bluehost.com
NSns2.bluehost.com
A162.159.25.175Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.bluehost.com
MXaspmx.l.google.com ⭐
A2a00:1450:4009:c0f::1b🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f27.1e100.net
A192.178.223.26🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2607:f8b0:4023:2801::1b🇺🇸 Google2607:f8b0::/32
PTRlcausi-in-f27.1e100.net
A192.178.128.26🇺🇸 Google192.178.128.0/24
PTRlcausi-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2607:f8b0:4023:1015::1a🇺🇸 Google2607:f8b0::/32
PTRyudfwta-in-f26.1e100.net
A172.253.135.27🇺🇸 Google172.253.135.0/24
PTRyudfwta-in-f27.1e100.net
MXalt3.aspmx.l.google.com(10)
A2a00:1450:4009:c0f::1a🇬🇧 Google2a00:1450:4009::/48
PTRyulhrs-in-f26.1e100.net
A192.178.223.27🇺🇸 Google192.178.223.0/24
PTRyulhrs-in-f27.1e100.net
MXalt4.aspmx.l.google.com(10)
A2a00:1450:4025:c01::1a🇵🇱 Google2a00:1450:4025::/48
PTRrd-in-f26.1e100.net
A142.250.147.26🇺🇸 Google142.250.147.0/24
PTRrd-in-f26.1e100.net
TXT_globalsign-domain-verification=7JPMxIidlHSoStYXm8askiRe4jztWpYAJslXIXi3oP
TXTv=spf1 +a +mx +ip4:50.87.238.54 +ip4:70.40.200.72 +include:bluehost.com ~all
TXTgoogle-site-verification=hdBHSUjoYY8RSRY3l00vhFHNCqX4y4GrbUOicpqNnTM
SOAns1.bluehost.comroot@box2423.bluehost.com 2026-01-31 #0

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1774387587

Same first word

brideaccess.com

DNS History

19 records (8 active, 11 former)

20162017201820192020202120222023202420252026NSns1.bluehost.comns2.bluehost.comdns1.registrar-servers.comdns1.registrar-servers.com,dns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comaspmx4.googlemail.comaspmx5.googlemail.comA70.40.200.72208.88.78.251
○NSdns1.registrar-servers.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○NSdns1.registrar-servers.com,2015-08-15 → 2016-03-20 · 4 obs
● 2015-08-15 03:15:00
● 2016-03-20 00:58:50
○ 2016-07-17 05:42:24
○ 2026-03-24 21:55:30
○NSdns2.registrar-servers.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○NSdns3.registrar-servers.com2015-08-15 → 2016-03-20 · 4 obs
● 2015-08-15 03:15:00
● 2016-03-20 00:58:50
○ 2016-07-17 05:42:24
○ 2026-03-24 21:55:30
○NSdns4.registrar-servers.com2015-08-15 → 2016-03-20 · 4 obs
● 2015-08-15 03:15:00
● 2016-03-20 00:58:50
○ 2016-07-17 05:42:24
○ 2026-03-24 21:55:30
○NSdns5.registrar-servers.com2015-08-15 → 2016-03-20 · 4 obs
● 2015-08-15 03:15:00
● 2016-03-20 00:58:50
○ 2016-07-17 05:42:24
○ 2026-03-24 21:55:30
●NSns1.bluehost.com2017-06-13 → 2026-03-24 · 3 obs
○ 2016-08-22 09:06:22
● 2017-06-13 02:15:38
● 2026-03-24 21:55:30
●NSns2.bluehost.com2017-06-13 → 2026-03-24 · 3 obs
○ 2016-08-22 09:06:22
● 2017-06-13 02:15:38
● 2026-03-24 21:55:30
●MXalt1.aspmx.l.google.com2015-08-15 → 2026-03-24 · 2 obs
● 2015-08-15 03:15:00
● 2026-03-24 21:55:30
●MXalt2.aspmx.l.google.com2015-08-15 → 2026-03-24 · 2 obs
● 2015-08-15 03:15:00
● 2026-03-24 21:55:30
●MXalt3.aspmx.l.google.com2017-06-13 → 2026-03-24 · 3 obs
○ 2016-08-22 09:06:22
● 2017-06-13 02:15:38
● 2026-03-24 21:55:30
●MXalt4.aspmx.l.google.com2017-06-13 → 2026-03-24 · 3 obs
○ 2016-08-22 09:06:22
● 2017-06-13 02:15:38
● 2026-03-24 21:55:30
●MXaspmx.l.google.com2015-08-15 → 2026-03-24 · 2 obs
● 2015-08-15 03:15:00
● 2026-03-24 21:55:30
○MXaspmx2.googlemail.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○MXaspmx3.googlemail.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○MXaspmx4.googlemail.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○MXaspmx5.googlemail.com2015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
○A208.88.78.2512015-08-15 → 2016-08-22 · 4 obs
● 2015-08-15 03:15:00
● 2016-08-22 09:06:22
○ 2017-06-13 02:15:38
○ 2026-03-24 21:55:30
●A70.40.200.722017-06-13 → 2026-03-24 · 3 obs
○ 2016-08-22 09:06:22
● 2017-06-13 02:15:38
● 2026-03-24 21:55:30

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comf.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net...-
brideaccess.comns1.bluehost.com, ns2.bluehost.com2 records

✅ Authoritative Response

Server:162.159.25.175

NS records: ns1.bluehost.com, ns2.bluehost.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for brideaccess.com (unsigned zone)

⏱️ Timing

Total: 286ms | Queries: -

📄 Records

TypeCountSample Data
A170.40.200.72
NS2ns2.bluehost.com, ns1.bluehost.com
MX5alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)...
TXT3_globalsign-domain-verification=7JPMxIid, v=spf1 +a +mx +ip4:50.87.238.54 +ip4:70....
SOA1ns1.bluehost.com root.box2423.bluehost.c

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)

Analysis

IP Addresses

brideaccess.com points to a single IP number: 70.40.200.72.

Name Servers

brideaccess.com is delegated to two name servers: ns1.bluehost.com and ns2.bluehost.com.

brideaccess.com shares the same name server setup as other domains, for example controlplus.biz, odonata-farm.com, meghanadeodhar.com, mediabatch.com and tiendasclick.com.

brideaccess.com partially shares name servers with other domains, for instance resiliencefairfield.com, flatratedrs.com, e-bursum.com and ptisg.com.

Host names with one IP number:

The host ns1.bluehost.com points to 162.159.24.80 and the host ns2.bluehost.com points to 162.159.25.175.

Mail Servers

brideaccess.com is handled by five mail servers: 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.

brideaccess.com shares mail servers with other domains at least partially, including annexlabnutrition.com, briankalakay.com, stadiumhelp.com, ccranelaw.com and dalkodiagnostics.com.

these mail servers are often used with the mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Hosts with two IP numbers:

aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.26.

alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1b and 192.178.128.26.

alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1a and 172.253.135.27.

alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.27.

alt4.aspmx.l.google.com points to 2a00:1450:4025:c01::1a and 142.250.147.26.