bridepage.com - robtex.com

bridepage.com

DNSSEC⚠️ Not signed
A2600:1f14:ea2:fa00:3b20:933a:f325:6239πŸ‡ΊπŸ‡Έ Amazon2600:1f14:800::/37 AMAZON AWS
A2600:1f14:ea2:fa01:9194:f8fd:e033:1e37πŸ‡ΊπŸ‡Έ Amazon2600:1f14:800::/37 AMAZON AWS
A35.167.174.32πŸ‡ΊπŸ‡Έ Amazon35.160.0.0/13 EC2 PDX prefix
A52.26.117.157πŸ‡ΊπŸ‡Έ Amazon52.24.0.0/14 EC2 PDX prefix
NSns1.venture.com ⭐
A34.217.229.194πŸ‡ΊπŸ‡Έ Amazon34.208.0.0/12 EC2 PDX prefix
PTRec2-34-217-229-194.us-west-2.compute.amazonaws.com
NSns2.venture.com
A44.226.97.88πŸ‡ΊπŸ‡Έ Amazon44.224.0.0/11 EC2 PDX prefix
PTRec2-44-226-97-88.us-west-2.compute.amazonaws.com
TXTv=spf1 -all
SOAns1.venture.comhostmaster@venture.com 2026-03-10 #13

com

DNS History

19 records (6 active, 13 former)

20162017201820192020202120222023202420252026NSns1.venture.comns2.venture.combuy.internettraffic.comns1.mark.comns1.uniregistrymarket.linkns2.mark.comns2.uniregistrymarket.linksell.internettraffic.comMXnullmx.bridepage.comA2600:1f14:ea2:fa00:3b20:933a:f325:62392600:1f14:ea2:fa01:9194:f8fd:e033:1e3735.167.174.3252.26.117.1572406:da00:ff00::36c5:f8012406:da00:ff00::36f3:64c754.197.248.154.243.100.19969.172.201.15369.172.201.208
β—‹NSbuy.internettraffic.com2015-10-21 β†’ 2016-07-15 Β· 5 obs
β—‹ 2015-05-27 09:12:52
● 2015-10-21 14:31:58
● 2016-07-15 17:50:08
β—‹ 2017-04-02 07:58:00
β—‹ 2026-03-12 04:10:58
β—‹NSns1.mark.com2015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹NSns1.uniregistrymarket.link2017-04-02 β†’ 2017-04-02 Β· 4 obs
β—‹ 2016-07-15 17:50:08
● 2017-04-02 07:58:00
β—‹ 2026-03-12 04:10:56
β—‹ 2026-03-12 04:10:58
●NSns1.venture.com2026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
β—‹NSns2.mark.com2015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹NSns2.uniregistrymarket.link2017-04-02 β†’ 2017-04-02 Β· 4 obs
β—‹ 2016-07-15 17:50:08
● 2017-04-02 07:58:00
β—‹ 2026-03-12 04:10:56
β—‹ 2026-03-12 04:10:58
●NSns2.venture.com2026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
β—‹NSsell.internettraffic.com2015-10-21 β†’ 2016-07-15 Β· 5 obs
β—‹ 2015-05-27 09:12:52
● 2015-10-21 14:31:58
● 2016-07-15 17:50:08
β—‹ 2017-04-02 07:58:00
β—‹ 2026-03-12 04:10:58
β—‹MXnullmx.bridepage.com2015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹A2406:da00:ff00::36c5:f8012015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹A2406:da00:ff00::36f3:64c72015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
●A2600:1f14:ea2:fa00:3b20:933a:f325:62392026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
●A2600:1f14:ea2:fa01:9194:f8fd:e033:1e372026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
●A35.167.174.322026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
●A52.26.117.1572026-03-12 β†’ 2026-03-12 Β· 3 obs
β—‹ 2017-04-02 07:58:00
● 2026-03-12 04:10:56
● 2026-03-12 04:10:58
β—‹A54.197.248.12015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹A54.243.100.1992015-05-27 β†’ 2015-05-27 Β· 3 obs
● 2015-05-27 09:12:52
β—‹ 2015-10-21 14:31:58
β—‹ 2026-03-12 04:10:58
β—‹A69.172.201.1532016-07-15 β†’ 2017-04-02 Β· 5 obs
β—‹ 2016-03-23 10:23:34
● 2016-07-15 17:50:08
● 2017-04-02 07:58:00
β—‹ 2026-03-12 04:10:56
β—‹ 2026-03-12 04:10:58
β—‹A69.172.201.2082015-10-21 β†’ 2016-03-23 Β· 5 obs
β—‹ 2015-05-27 09:12:52
● 2015-10-21 14:31:58
● 2016-03-23 10:23:34
β—‹ 2016-07-15 17:50:08
β—‹ 2026-03-12 04:10:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...-
bridepage.comns2.venture.com, ns1.venture.com2 records

βœ… Authoritative Response

Server: 44.226.97.88

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bridepage.com (unsigned zone)

⏱️ Timing

Total: 212ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A252.26.117.157, 35.167.174.32
AAAA22600:1f14:ea2:fa01:9194:f8fd:e033:1e37, 2600:1f14:ea2:fa00:3b20:933a:f325:6239
NS2ns2.venture.com, ns1.venture.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1.venture.com hostmaster.venture.com

πŸ“Œ Glue Records Collected

Total: 2

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

Analysis

IP Addresses

bridepage.com points to four IP numbers: 2600:1f14:ea2:fa00:3b20:933a:f325:6239, 2600:1f14:ea2:fa01:9194:f8fd:e033:1e37, 35.167.174.32 and 52.26.117.157.

For instance, other host names www.asqc.com, wpka.com, bfbd.com, madeena.com and bannerdisplay.com share IP numbers with bridepage.com.

Name Servers

bridepage.com is delegated to two name servers: ns1.venture.com and ns2.venture.com.

bridepage.com uses the same name server setup as other domains such as whatishappening.com, inpu.com, sorefeet.com, hoteldeals.com and thinkthin.com.

Host names with one IP number:

ns1.venture.com points to: 34.217.229.194.

ns2.venture.com points to: 44.226.97.88.