bridalspace.com - dns.ninja

bridalspace.com

com

WOT: UNKNOWN (61/100)

Previously MX for

Subdomains

Same first word

Similar names

DNS History

33 records (4 active, 29 former)

2008201020122014201620182020202220242026NSns1.afternic.comns2.afternic.comdns1.name-services.comdns2.name-services.comdns3.name-services.comdns4.name-services.comdns5.name-services.comns01.cashparking.comns02.cashparking.comns1.thinklogic.cans1.uniregistrymarket.linkns2.thinklogic.cans2.uniregistrymarket.linkns578.dizinc.comns579.dizinc.comverification-afdauqilq5jwnup6uxczbv.ns101.verify.hnverification-jzfegusxepfgttto3cnjng.ns101.verify.hnMX.alt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comaspmx4.googlemail.comaspmx5.googlemail.combridalspace.comA13.248.169.4876.223.54.14615.197.204.563.33.243.14569.172.201.15372.29.73.12372.89.59.69
β—‹NSdns1.name-services.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹NSdns2.name-services.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹NSdns3.name-services.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹NSdns4.name-services.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹NSdns5.name-services.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹NSns01.cashparking.com2026-03-13 β†’ 2026-05-04 Β· 5 obs
β—‹ 2017-07-05 03:30:28
● 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
β—‹NSns02.cashparking.com2026-03-13 β†’ 2026-05-04 Β· 5 obs
β—‹ 2017-07-05 03:30:28
● 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
●NSns1.afternic.com2026-06-24 β†’ 2026-06-24 Β· 3 obs
β—‹ 2026-05-04 22:20:04
● 2026-06-24 09:41:16
● 2026-06-24 09:41:18
β—‹NSns1.thinklogic.ca2007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
β—‹NSns1.uniregistrymarket.link2017-07-05 β†’ 2017-07-05 Β· 4 obs
β—‹ 2016-09-10 02:52:10
● 2017-07-05 03:30:28
β—‹ 2026-03-13 10:13:32
β—‹ 2026-06-24 09:41:18
●NSns2.afternic.com2026-06-24 β†’ 2026-06-24 Β· 3 obs
β—‹ 2026-05-04 22:20:04
● 2026-06-24 09:41:16
● 2026-06-24 09:41:18
β—‹NSns2.thinklogic.ca2007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
β—‹NSns2.uniregistrymarket.link2017-07-05 β†’ 2017-07-05 Β· 4 obs
β—‹ 2016-09-10 02:52:10
● 2017-07-05 03:30:28
β—‹ 2026-03-13 10:13:32
β—‹ 2026-06-24 09:41:18
β—‹NSns578.dizinc.com2007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
β—‹NSns579.dizinc.com2007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
β—‹NSverification-afdauqilq5jwnup6uxczbv.ns101.verify.hn2026-03-13 β†’ 2026-05-04 Β· 5 obs
β—‹ 2017-07-05 03:30:28
● 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
β—‹NSverification-jzfegusxepfgttto3cnjng.ns101.verify.hn2026-05-04 β†’ 2026-05-04 Β· 4 obs
β—‹ 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
β—‹MX.2026-03-13 β†’ 2026-06-24 Β· 2 obs
β—‹ 2026-03-13 10:13:32
β—‹ 2026-06-24 09:41:18
β—‹MXalt1.aspmx.l.google.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXalt2.aspmx.l.google.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXaspmx.l.google.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXaspmx2.googlemail.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXaspmx3.googlemail.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXaspmx4.googlemail.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXaspmx5.googlemail.com2015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
β—‹MXbridalspace.com2007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
●A13.248.169.482026-06-24 β†’ 2026-06-24 Β· 3 obs
β—‹ 2026-05-04 22:20:04
● 2026-06-24 09:41:16
● 2026-06-24 09:41:18
β—‹A15.197.204.562026-03-13 β†’ 2026-05-04 Β· 5 obs
β—‹ 2017-07-05 03:30:28
● 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
β—‹A3.33.243.1452026-03-13 β†’ 2026-05-04 Β· 5 obs
β—‹ 2017-07-05 03:30:28
● 2026-03-13 10:13:32
● 2026-05-04 22:20:04
β—‹ 2026-06-24 09:41:16
β—‹ 2026-06-24 09:41:18
β—‹A69.172.201.1532017-07-05 β†’ 2017-07-05 Β· 4 obs
β—‹ 2016-09-10 02:52:10
● 2017-07-05 03:30:28
β—‹ 2026-03-13 10:13:32
β—‹ 2026-06-24 09:41:18
β—‹A72.29.73.1232007-10-31 β†’ 2007-10-31 Β· 3 obs
● 2007-10-31 14:19:00
β—‹ 2015-06-16 09:29:28
β—‹ 2026-06-24 09:41:18
β—‹A72.89.59.692015-06-16 β†’ 2016-09-10 Β· 5 obs
β—‹ 2007-10-31 14:19:00
● 2015-06-16 09:29:28
● 2016-09-10 02:52:10
β—‹ 2017-07-05 03:30:28
β—‹ 2026-06-24 09:41:18
●A76.223.54.1462026-06-24 β†’ 2026-06-24 Β· 3 obs
β—‹ 2026-05-04 22:20:04
● 2026-06-24 09:41:16
● 2026-06-24 09:41:18

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
bridalspace.comns1.afternic.com, ns2.afternic.com4 records

βœ… Authoritative Response

Server:97.74.98.69

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bridalspace.com (unsigned zone)

⏱️ Timing

Total: 243ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A276.223.54.146, 13.248.169.48
NS2ns1.afternic.com, ns2.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns1.afternic.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

The domain www.bridalspace.com falls under the parent bridalspace.com.

IP Addresses

bridalspace.com points to the IP addresses 13.248.169.48 and 76.223.54.146

transvestitephotos.com, topshrimp.com, rein.co.nz plus two other host names have IP numbers in common with bridalspace.com.

Name Servers

bridalspace.com is delegated to two name servers: ns1.afternic.com and ns2.afternic.com.

The name server configuration of bridalspace.com is shared with other domains, for instance hohum.com, oop.com, mail.durocrete.com and two others.

At least some of bridalspace.com's name servers are shared with other domains, for example iidf.com, reifier.com, movedigit.com and two more.

These name servers tend to appear together with the name servers verification-8wuq9clyoujvhmmdvmhsax.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, plus two others.

ns1.afternic.com and ns2.afternic.com each resolve to two IP addresses: ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45, while ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45.