weddingcloud.com - dns.ninja

weddingcloud.com

DNSSEC⚠️ Not signed
NSns1.dns.ministrybrands.com ⭐
A2600:9000:5302:5400::1🇺🇸 Amazon2600:9000:5302::/48 - CloudFront
PTRns-596.awsdns-10.net
A205.251.194.84🇺🇸 Amazon205.251.194.0/24 prefix
PTRns-596.awsdns-10.net
NSns2.dns.ministrybrands.com
A2600:9000:5306:7c00::1🇺🇸 Amazon2600:9000:5306::/48 - CloudFront
PTRns-1660.awsdns-15.co.uk
A205.251.198.124🇺🇸 Amazon205.251.198.0/24 prefix
PTRns-1660.awsdns-15.co.uk
NSns3.dns.ministrybrands.com
A2600:9000:5300:ec00::1🇺🇸 Amazon2600:9000:5300::/48 - CloudFront
PTRns-236.awsdns-29.com
A205.251.192.236🇺🇸 Amazon205.251.192.0/24 prefix
PTRns-236.awsdns-29.com
NSns4.dns.ministrybrands.com
A2600:9000:5305:8700::1🇺🇸 Amazon2600:9000:5305::/48 - CloudFront
PTRns-1415.awsdns-48.org
A205.251.197.135🇺🇸 Amazon205.251.197.0/24 prefix
PTRns-1415.awsdns-48.org
TXTv=spf1 -all
SOAns1.dns.ministrybrands.comawsdns-hostmaster@amazon.com serial=1

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=1785650107

Same first word

weddingcloud.com
weddingcloud.jp
weddingcloud.in
weddingcloud.me

Similar names

cloudwedding.xyz
cloudwedding.com

DNS History

18 records (4 active, 14 former)

20162017201820192020202120222023202420252026NSns1.dns.ministrybrands.comns2.dns.ministrybrands.comns3.dns.ministrybrands.comns4.dns.ministrybrands.comdns1.name-services.comdns1.registrar-servers.comdns2.name-services.comdns2.registrar-servers.comdns3.name-services.comdns3.registrar-servers.comdns4.name-services.comdns4.registrar-servers.comdns5.name-services.comdns5.registrar-servers.comMXmail.3prophets.comA45.79.85.7898.124.204.16CNAME3prophets.com
○NSdns1.name-services.com2016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○NSdns1.registrar-servers.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○NSdns2.name-services.com2016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○NSdns2.registrar-servers.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○NSdns3.name-services.com2016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○NSdns3.registrar-servers.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○NSdns4.name-services.com2016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○NSdns4.registrar-servers.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○NSdns5.name-services.com2016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○NSdns5.registrar-servers.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
●NSns1.dns.ministrybrands.com2026-04-01 → 2026-08-02 · 3 obs
○ 2017-05-16 05:55:04
● 2026-04-01 23:52:38
● 2026-08-02 05:57:08
●NSns2.dns.ministrybrands.com2026-04-01 → 2026-08-02 · 3 obs
○ 2017-05-16 05:55:04
● 2026-04-01 23:52:38
● 2026-08-02 05:57:08
●NSns3.dns.ministrybrands.com2026-04-01 → 2026-08-02 · 3 obs
○ 2017-05-16 05:55:04
● 2026-04-01 23:52:38
● 2026-08-02 05:57:08
●NSns4.dns.ministrybrands.com2026-04-01 → 2026-08-02 · 3 obs
○ 2017-05-16 05:55:04
● 2026-04-01 23:52:38
● 2026-08-02 05:57:08
○MXmail.3prophets.com2015-12-06 → 2017-05-16 · 6 obs
● 2015-12-06 03:09:24
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○A45.79.85.782015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08
○A98.124.204.162016-08-07 → 2016-08-07 · 4 obs
○ 2016-03-14 16:39:32
● 2016-08-07 20:15:48
○ 2017-05-16 05:55:04
○ 2026-08-02 05:57:08
○CNAME3prophets.com2015-08-09 → 2017-05-16 · 6 obs
● 2015-08-09 19:34:06
● 2016-03-14 16:39:32
○ 2016-08-07 20:15:48
● 2017-05-16 05:55:04
○ 2026-04-01 23:52:38
○ 2026-08-02 05:57:08

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comj.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net...-
weddingcloud.comns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com, ns3.dns.ministrybrands.com, ns4.dns.ministrybrands.com8 records

✅ Authoritative Response

Server:205.251.194.84

NS records: ns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com, ns3.dns.ministrybrands.com, ns4.dns.ministrybrands.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingcloud.com (unsigned zone)

⏱️ Timing

Total: 144ms | Queries: -

📄 Records

TypeCountSample Data
NS4ns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com...
TXT1v=spf1 -all
SOA1ns1.dns.ministrybrands.com awsdns-hostma

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.dns.ministrybrands.com, ns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com...)

Analysis

Name Servers

The authoritative name servers for weddingcloud.com are ns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com, ns3.dns.ministrybrands.com and ns4.dns.ministrybrands.com.

There is at least partial name server overlap between weddingcloud.com and other domains — clovergive.com, churchnurserysecurity.info, monkcms.com and two more among them.

All four hostnames — ns1.dns.ministrybrands.com, ns2.dns.ministrybrands.com, ns3.dns.ministrybrands.com and ns4.dns.ministrybrands.com — resolve to two IP numbers apiece: ns1.dns.ministrybrands.com to 205.251.194.84 and 2600:9000:5302:5400::1; ns2.dns.ministrybrands.com to 205.251.198.124 and 2600:9000:5306:7c00::1; ns3.dns.ministrybrands.com to 205.251.192.236 and 2600:9000:5300:ec00::1; ns4.dns.ministrybrands.com to 205.251.197.135 and 2600:9000:5305:8700::1.