Verifying against the live site and live WHOIS/DNS…
Common questions
Is weddingchannel.com legit or a scam?
AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns weddingchannel.com?
Nobody has completed AboutUs's owner verification for weddingchannel.com. That's true of most sites here — it isn't itself a warning sign.
Correct a description, link or other detail. Submissions are reviewed before publication.
The site's bot protection blocked AboutUs's HTTPS check; all 1 of the other checks passed (Nov 1, 2026).
Registered 1998 · AboutUs's live check was blocked by the site's bot protection
WeddingChannel.com
The #1 website for weddings featuring wedding gowns, bridal gift registry, wedding etiquette and advice, invitations, bridesmaids dresses, wedding planning ideas, vows, music, photography and much more!
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 28 years ago · on AboutUs since 2006 · 1 registrar change since Jul 15, 2011 · 4 registrant changes since 2007 · last checked Nov 1, 2026.
Registration
RegisteredAug 19, 1998weddingchannel.com was registered on Aug 19, 1998.Source: RDAP, fetched Aug 23, 2026
AboutUs record
AboutUs wiki pageAboutUs wiki pageJun 21, 2006 – Aug 6, 2012An AboutUs wiki page described weddingchannel.com from Jun 21, 2006 to Aug 6, 2012 (8 edits).Source: AboutUs wiki archive, 2006–2023Said about itself in 2006Jul 1, 2006“The #1 website for weddings featuring wedding gowns, bridal gift registry, wedding etiquette and advice, invitations, bridesmaids dresses, wedding planning ideas, vows, music, photography and much more!”Source: AboutUs wiki archive, 2006Current AboutUs recordJun 25, 2026 – Aug 23, 2026 (latest)Authority and Safety last refreshed Aug 23, 2026.Source: AboutUs checks
Registrar
GoDaddy.com, LLCGoDaddy.com, LLCJul 15, 2011 – Oct 16, 2022Registrar GoDaddy.com, LLC (IANA 146) in the WHOIS and RDAP records held for weddingchannel.com, from Jul 15, 2011 to Oct 16, 2022.Source: WHOIS / RDAP archive (who.is)GoDaddy Corporate Domains, LLCGoDaddy Corporate Domains, LLCDec 2, 2022 – Oct 31, 2026 (latest)Registrar GoDaddy Corporate Domains, LLC (IANA 3786) in the registration data recorded, first on Dec 2, 2022 and most recently on Oct 31, 2026.Source: RDAP, fetched Aug 23, 2026
Registrant
Registrant recordsMay 19, 2007 – Jun 3, 2026Registration records for weddingchannel.com are held from May 19, 2007 to Jun 3, 2026 (185 records). 4 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization onlyRegistrant changeJun 4, 2008The registrant name or organization in the registration record changed; first recorded Jun 4, 2008. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization onlyRegistrant changeFeb 14, 2011The registrant name or organization in the registration record changed; first recorded Feb 14, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization onlyRegistrant changeJan 9, 2012The registrant name or organization in the registration record changed; first recorded Jan 9, 2012. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization onlyRegistrant changeDec 2, 2022The registrant name or organization in the registration record changed; first recorded Dec 2, 2022. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
4 registrant changes, 2007–2026
Zone file
No nameserver records held, Feb 2009 – Jul 2011No nameserver records held, Jan 2017 – Apr 2018No nameserver records held, Mar 2024 – Jun 2025Nameservers: weddingchannel.comMay 19, 2007 – Feb 4, 2009Registration records listed weddingchannel.com nameservers (ns1.weddingchannel.com) for weddingchannel.com from May 19, 2007 to Feb 4, 2009.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: theknot.comJul 15, 2011 – Jan 27, 2012Registration records listed theknot.com nameservers (ns1.theknot.com, ns2.theknot.com) for weddingchannel.com from Jul 15, 2011 to Jan 27, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to theknot.comJul 15, 2011weddingchannel.com's nameservers moved from weddingchannel.com to theknot.com at some point between Feb 4, 2009 and Jul 15, 2011. Last seen at weddingchannel.com: Feb 4, 2009 (registration record). First seen at theknot.com: Jul 15, 2011 (registration record). AboutUs holds no nameserver records for the about 2 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: Oracle DynApr 23, 2012Registration records listed Oracle Dyn nameservers (ns1.p20.dynect.net, ns1.theknot.com, ns2.p20.dynect.net…) for weddingchannel.com from Apr 23, 2012 to Apr 23, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to Oracle DynApr 23, 2012weddingchannel.com's nameservers moved from theknot.com to Oracle Dyn at some point between Jan 27, 2012 and Apr 23, 2012. Last seen at theknot.com: Jan 27, 2012 (registration record). First seen at Oracle Dyn: Apr 23, 2012 (registration record). AboutUs holds no nameserver records for the 3 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: theknot.comMay 10, 2012 – May 23, 2012Registration records listed theknot.com nameservers (ns1.theknot.com) for weddingchannel.com from May 10, 2012 to May 23, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to theknot.comMay 10, 2012weddingchannel.com's nameservers moved from Oracle Dyn to theknot.com between Apr 23, 2012 and May 10, 2012. Last seen at Oracle Dyn: Apr 23, 2012 (registration record). First seen at theknot.com: May 10, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: Oracle DynJun 16, 2012 – Oct 17, 2013Registration records listed Oracle Dyn nameservers (ns3.p20.dynect.net) for weddingchannel.com from Jun 16, 2012 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to Oracle DynJun 16, 2012weddingchannel.com's nameservers moved from theknot.com to Oracle Dyn between May 23, 2012 and Jun 16, 2012. Last seen at theknot.com: May 23, 2012 (registration record). First seen at Oracle Dyn: Jun 16, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: Oracle DynOct 18, 2013 – Apr 1, 2016Oracle Dyn (ns1.p20.dynect.net, ns2.p20.dynect.net, ns3.p20.dynect.net…) were the nameservers listed for weddingchannel.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)Nameservers: Oracle DynApr 2, 2016 – Jul 10, 2016Registration records listed Oracle Dyn nameservers (ns3.p20.dynect.net) for weddingchannel.com from Apr 2, 2016 to Jul 10, 2016. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: Amazon Route 53Jan 30, 2017Registration records listed Amazon Route 53 nameservers (ns-1003.awsdns-61.net, ns-109.awsdns-13.com, ns-1283.awsdns-32.org…) for weddingchannel.com from Jan 30, 2017 to Jan 30, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to Amazon Route 53Jan 30, 2017weddingchannel.com's nameservers moved from Oracle Dyn to Amazon Route 53 at some point between Jul 10, 2016 and Jan 30, 2017. Last seen at Oracle Dyn: Jul 10, 2016 (registration record). First seen at Amazon Route 53: Jan 30, 2017 (registration record). AboutUs holds no nameserver records for the 7 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: GoDaddyApr 3, 2018GoDaddy (pdns11.domaincontrol.com, pdns12.domaincontrol.com) were the nameservers listed for weddingchannel.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)DNS moved to GoDaddyApr 3, 2018weddingchannel.com's nameservers moved from Amazon Route 53 to GoDaddy at some point between Jan 30, 2017 and Apr 3, 2018. Last seen at Amazon Route 53: Jan 30, 2017 (registration record). First seen at GoDaddy: Apr 3, 2018 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 14 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → ICANN zone-file snapshot)Nameservers: GoDaddyJun 20, 2018 – Oct 16, 2022Registration records listed GoDaddy nameservers (pdns11.domaincontrol.com, pdns12.domaincontrol.com) for weddingchannel.com from Jun 20, 2018 to Oct 16, 2022.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: brandsight-dns.com, brandsight-dns.netDec 2, 2022 – Mar 14, 2024Registration records listed brandsight-dns.com, brandsight-dns.net nameservers (ns1.brandsight-dns.com, ns1.brandsight-dns.net, ns2.brandsight-dns.com…) for weddingchannel.com from Dec 2, 2022 to Mar 14, 2024.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to brandsight-dns.com, brandsight-dns.netDec 2, 2022weddingchannel.com's nameservers moved from GoDaddy to brandsight-dns.com, brandsight-dns.net at some point between Oct 16, 2022 and Dec 2, 2022. Last seen at GoDaddy: Oct 16, 2022 (registration record). First seen at brandsight-dns.com, brandsight-dns.net: Dec 2, 2022 (registration record). AboutUs holds no nameserver records for the 47 days in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: gcd-dns.comJun 27, 2025 – Jun 3, 2026Registration records listed gcd-dns.com nameservers (ns13.gcd-dns.com, ns14.gcd-dns.com) for weddingchannel.com from Jun 27, 2025 to Jun 3, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to gcd-dns.comJun 27, 2025weddingchannel.com's nameservers moved from brandsight-dns.com, brandsight-dns.net to gcd-dns.com at some point between Mar 14, 2024 and Jun 27, 2025. Last seen at brandsight-dns.com, brandsight-dns.net: Mar 14, 2024 (registration record). First seen at gcd-dns.com: Jun 27, 2025 (registration record). AboutUs holds no nameserver records for the 15 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)Seen in the .com zone fileSep 8, 2026 – Nov 1, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns13.gcd-dns.com, ns14.gcd-dns.com.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Certificate
GoDaddy.comFeb 16, 2026 – Nov 1, 2026 (latest)GoDaddy.com issued 4 certificates for weddingchannel.com from Feb 16, 2026, the latest valid until Jan 28, 2027. Seen in use on Oct 31, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 31, 2026Let's EncryptMay 15, 2026 – Nov 1, 2026Let's Encrypt issued 6 certificates for weddingchannel.com from May 15, 2026, the latest valid until Dec 10, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
200020102020Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (34)
Aug 19, 1998Registration: weddingchannel.com was registered on Aug 19, 1998.Source: RDAP, fetched Aug 23, 2026
Jun 21, 2006 – Aug 6, 2012AboutUs record: An AboutUs wiki page described weddingchannel.com from Jun 21, 2006 to Aug 6, 2012 (8 edits).Source: AboutUs wiki archive, 2006–2023
Jul 1, 2006AboutUs record: “The #1 website for weddings featuring wedding gowns, bridal gift registry, wedding etiquette and advice, invitations, bridesmaids dresses, wedding planning ideas, vows, music, photography and much more!”Source: AboutUs wiki archive, 2006
May 19, 2007 – Jun 3, 2026Registrant: Registration records for weddingchannel.com are held from May 19, 2007 to Jun 3, 2026 (185 records). 4 changes of registrant name or organization are marked. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
May 19, 2007 – Feb 4, 2009Zone file: Registration records listed weddingchannel.com nameservers (ns1.weddingchannel.com) for weddingchannel.com from May 19, 2007 to Feb 4, 2009.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 4, 2008Registrant: The registrant name or organization in the registration record changed; first recorded Jun 4, 2008. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Feb 14, 2011Registrant: The registrant name or organization in the registration record changed; first recorded Feb 14, 2011. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Jul 15, 2011 – Oct 16, 2022Registrar: Registrar GoDaddy.com, LLC (IANA 146) in the WHOIS and RDAP records held for weddingchannel.com, from Jul 15, 2011 to Oct 16, 2022.Source: WHOIS / RDAP archive (who.is)
Jul 15, 2011 – Jan 27, 2012Zone file: Registration records listed theknot.com nameservers (ns1.theknot.com, ns2.theknot.com) for weddingchannel.com from Jul 15, 2011 to Jan 27, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 15, 2011Zone file: weddingchannel.com's nameservers moved from weddingchannel.com to theknot.com at some point between Feb 4, 2009 and Jul 15, 2011. Last seen at weddingchannel.com: Feb 4, 2009 (registration record). First seen at theknot.com: Jul 15, 2011 (registration record). AboutUs holds no nameserver records for the about 2 years in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jan 9, 2012Registrant: The registrant name or organization in the registration record changed; first recorded Jan 9, 2012. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 23, 2012Zone file: Registration records listed Oracle Dyn nameservers (ns1.p20.dynect.net, ns1.theknot.com, ns2.p20.dynect.net…) for weddingchannel.com from Apr 23, 2012 to Apr 23, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 23, 2012Zone file: weddingchannel.com's nameservers moved from theknot.com to Oracle Dyn at some point between Jan 27, 2012 and Apr 23, 2012. Last seen at theknot.com: Jan 27, 2012 (registration record). First seen at Oracle Dyn: Apr 23, 2012 (registration record). AboutUs holds no nameserver records for the 3 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
May 10, 2012 – May 23, 2012Zone file: Registration records listed theknot.com nameservers (ns1.theknot.com) for weddingchannel.com from May 10, 2012 to May 23, 2012.Source: From registration records (WHOIS / RDAP archive, who.is)
May 10, 2012Zone file: weddingchannel.com's nameservers moved from Oracle Dyn to theknot.com between Apr 23, 2012 and May 10, 2012. Last seen at Oracle Dyn: Apr 23, 2012 (registration record). First seen at theknot.com: May 10, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 16, 2012 – Oct 17, 2013Zone file: Registration records listed Oracle Dyn nameservers (ns3.p20.dynect.net) for weddingchannel.com from Jun 16, 2012 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 16, 2012Zone file: weddingchannel.com's nameservers moved from theknot.com to Oracle Dyn between May 23, 2012 and Jun 16, 2012. Last seen at theknot.com: May 23, 2012 (registration record). First seen at Oracle Dyn: Jun 16, 2012 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Oct 18, 2013 – Apr 1, 2016Zone file: Oracle Dyn (ns1.p20.dynect.net, ns2.p20.dynect.net, ns3.p20.dynect.net…) were the nameservers listed for weddingchannel.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Apr 2, 2016 – Jul 10, 2016Zone file: Registration records listed Oracle Dyn nameservers (ns3.p20.dynect.net) for weddingchannel.com from Apr 2, 2016 to Jul 10, 2016. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jan 30, 2017Zone file: Registration records listed Amazon Route 53 nameservers (ns-1003.awsdns-61.net, ns-109.awsdns-13.com, ns-1283.awsdns-32.org…) for weddingchannel.com from Jan 30, 2017 to Jan 30, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)
Jan 30, 2017Zone file: weddingchannel.com's nameservers moved from Oracle Dyn to Amazon Route 53 at some point between Jul 10, 2016 and Jan 30, 2017. Last seen at Oracle Dyn: Jul 10, 2016 (registration record). First seen at Amazon Route 53: Jan 30, 2017 (registration record). AboutUs holds no nameserver records for the 7 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Apr 3, 2018Zone file: GoDaddy (pdns11.domaincontrol.com, pdns12.domaincontrol.com) were the nameservers listed for weddingchannel.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Apr 3, 2018Zone file: weddingchannel.com's nameservers moved from Amazon Route 53 to GoDaddy at some point between Jan 30, 2017 and Apr 3, 2018. Last seen at Amazon Route 53: Jan 30, 2017 (registration record). First seen at GoDaddy: Apr 3, 2018 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 14 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → ICANN zone-file snapshot)
Jun 20, 2018 – Oct 16, 2022Zone file: Registration records listed GoDaddy nameservers (pdns11.domaincontrol.com, pdns12.domaincontrol.com) for weddingchannel.com from Jun 20, 2018 to Oct 16, 2022.Source: From registration records (WHOIS / RDAP archive, who.is)
Dec 2, 2022 – Oct 31, 2026Registrar: Registrar GoDaddy Corporate Domains, LLC (IANA 3786) in the registration data recorded, first on Dec 2, 2022 and most recently on Oct 31, 2026.Source: RDAP, fetched Aug 23, 2026
Dec 2, 2022Registrant: The registrant name or organization in the registration record changed; first recorded Dec 2, 2022. That can be a rename, a new contact or a sale; the record alone does not say which.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Dec 2, 2022 – Mar 14, 2024Zone file: Registration records listed brandsight-dns.com, brandsight-dns.net nameservers (ns1.brandsight-dns.com, ns1.brandsight-dns.net, ns2.brandsight-dns.com…) for weddingchannel.com from Dec 2, 2022 to Mar 14, 2024.Source: From registration records (WHOIS / RDAP archive, who.is)
Dec 2, 2022Zone file: weddingchannel.com's nameservers moved from GoDaddy to brandsight-dns.com, brandsight-dns.net at some point between Oct 16, 2022 and Dec 2, 2022. Last seen at GoDaddy: Oct 16, 2022 (registration record). First seen at brandsight-dns.com, brandsight-dns.net: Dec 2, 2022 (registration record). AboutUs holds no nameserver records for the 47 days in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 27, 2025 – Jun 3, 2026Zone file: Registration records listed gcd-dns.com nameservers (ns13.gcd-dns.com, ns14.gcd-dns.com) for weddingchannel.com from Jun 27, 2025 to Jun 3, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 27, 2025Zone file: weddingchannel.com's nameservers moved from brandsight-dns.com, brandsight-dns.net to gcd-dns.com at some point between Mar 14, 2024 and Jun 27, 2025. Last seen at brandsight-dns.com, brandsight-dns.net: Mar 14, 2024 (registration record). First seen at gcd-dns.com: Jun 27, 2025 (registration record). AboutUs holds no nameserver records for the 15 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Feb 16, 2026 – Nov 1, 2026Certificate: GoDaddy.com issued 4 certificates for weddingchannel.com from Feb 16, 2026, the latest valid until Jan 28, 2027. Seen in use on Oct 31, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 31, 2026
May 15, 2026 – Nov 1, 2026Certificate: Let's Encrypt issued 6 certificates for weddingchannel.com from May 15, 2026, the latest valid until Dec 10, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Jun 25, 2026 – Aug 23, 2026AboutUs record: Authority and Safety last refreshed Aug 23, 2026.Source: AboutUs checks
Sep 8, 2026 – Nov 1, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 1, 2026. Nameservers on Nov 1, 2026: ns13.gcd-dns.com, ns14.gcd-dns.com.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Automated safety checks
DNS (passed)
AboutUs has not vetted this site. Everything below is what we could measure automatically. Anything you do on the site — paying, sharing personal details, downloading — is between you and the site, not AboutUs.
Current facts
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
latest result
Domain registered Aug 19, 1998 — 28 years old.
latest result
Registrar on record: GoDaddy Corporate Domains, LLC — unchanged since AboutUs began tracking (Aug 29, 2026).
Authority 48/100— ahead of 48% of the August 2026 scored sampleClear
Why this authority score
48 is a percentile: higher than 48% of sites we score.
How it's calculated
Prominence (Tranco rank #328,471)+5
Verified continuity: 28.2 years (RDAP registration)+11
Security & email hygiene+2
Calibration adjustment (published map)+8
Model score: 26/99 — what these reason lines add up to.
Published Authority (percentile): 48/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
No unexpired threat-feed result; name-similarity check available (recorded about 70 days ago); 3/3 transport and email checks available (oldest recorded about 70 days ago). This is evidence coverage, not a probability that a website is safe.
No MX and no DMARC (mild)
What weddingchannel.com said about itself, 2006
Quoted from the site's AboutUs wiki page in each year it changed (1 version). These are the page's own words at the time, not AboutUs's assessment. New words · dropped words
2006
The #1 website for weddings featuring wedding gowns, bridal gift registry, wedding etiquette and advice, invitations, bridesmaids dresses, wedding planning ideas, vows, music, photography and much more!
Site history
Dated record — historical facts always carry their date.
1998
Domain registered (Aug 19, 1998).
2026
Checked today — The site's bot protection blocked AboutUs's HTTPS check; all 1 of the other checks passed (Nov 1, 2026).
✓ domain continuity 28 years registered– live check blocked the site's bot protection turned the check away Nov 1, 2026