Verifying against the live site and live WHOIS/DNS…
Common questions
Is mywedding.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 mywedding.com?
Nobody has completed AboutUs's owner verification for mywedding.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.
1 of 2 safety checks passed (Nov 1, 2026).
Registered 1998 · AboutUs could not get a response over HTTPS when it checked (Nov 1, 2026)
MyWedding.com provides info resources for wedding planning
MyWedding.com is a wedding planning directory and resource guide that helps users find vendors and services including photographers, reception facilities, ceremony sites, cakes, and dresses. The site is operated by Pacifica Internet Technologies, LLC and serves couples planning weddings.
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 28 years ago · on AboutUs since 2006 · 2 registrar changes since Sep 10, 2011 · 4 registrant changes since 2007 · last checked Nov 1, 2026.
Registration
RegisteredJul 11, 1998mywedding.com was registered on Jul 11, 1998.Source: RDAP, fetched Aug 23, 2026
AboutUs record
AboutUs wiki pageAboutUs wiki pageJun 21, 2006 – Nov 7, 2013An AboutUs wiki page described mywedding.com from Jun 21, 2006 to Nov 7, 2013 (3 edits).Source: AboutUs wiki archive, 2006–2023Said about itself in 2006Jul 1, 2006“Your complete wedding planning guide. Find wedding photographers, wedding reception facilities, wedding ceremony sites, wedding cakes, wedding dresses, and more!”Source: AboutUs wiki archive, 2006Current AboutUs recordJul 14, 2026 – Aug 23, 2026 (latest)Authority and Safety last refreshed Aug 23, 2026.Source: AboutUs checks
Registrar
ENOM, INC.Sep 10, 2011 – Jun 10, 2014Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for mywedding.com, from Sep 10, 2011 to Jun 10, 2014.Source: WHOIS / RDAP archive (who.is)TUCOWS, INC.Jul 20, 2016 – Jul 23, 2018Registrar TUCOWS, INC. (IANA 69) in the WHOIS and RDAP records held for mywedding.com, from Jul 20, 2016 to Jul 23, 2018.Source: WHOIS / RDAP archive (who.is)MarkMonitor, Inc.MarkMonitor, Inc.Aug 13, 2018 – Oct 7, 2026 (latest)Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Aug 13, 2018 and most recently on Oct 7, 2026.Source: RDAP, fetched Aug 23, 2026
Registrant
Registrant recordsMay 17, 2007 – May 16, 2026Registration records for mywedding.com are held from May 17, 2007 to May 16, 2026 (575 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 6, 2009The registrant name or organization in the registration record changed; first recorded Jun 6, 2009. 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 changeMar 28, 2013The registrant name or organization in the registration record changed; first recorded Mar 28, 2013. 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 changeJul 20, 2016The registrant name or organization in the registration record changed; first recorded Jul 20, 2016. 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 changeJul 26, 2022The registrant name or organization in the registration record changed; first recorded Jul 26, 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
Nameservers: UltraDNS (Neustar/Vercara)May 17, 2007 – Apr 11, 2008Registration records listed UltraDNS (Neustar/Vercara) nameservers (udns1.ultradns.net) for mywedding.com from May 17, 2007 to Apr 11, 2008.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: DNS Made EasyNameservers: DNS Made EasyApr 15, 2008 – Oct 17, 2013Registration records listed DNS Made Easy nameservers (ns0.dnsmadeeasy.com) for mywedding.com from Apr 15, 2008 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 DNS Made EasyApr 15, 2008mywedding.com's nameservers moved from UltraDNS (Neustar/Vercara) to DNS Made Easy between Apr 11, 2008 and Apr 15, 2008. Last seen at UltraDNS (Neustar/Vercara): Apr 11, 2008 (registration record). First seen at DNS Made Easy: Apr 15, 2008 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)Nameservers: DNS Made EasyOct 18, 2013 – Jan 24, 2015DNS Made Easy (ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com…) were the nameservers listed for mywedding.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Jan 24, 2015 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)Nameservers: UltraDNS (Neustar/Vercara)Mar 27, 2015 – Apr 3, 2018UltraDNS (Neustar/Vercara) (pdns152.ultradns.biz, pdns152.ultradns.com, pdns152.ultradns.net…) were the nameservers listed for mywedding.com at every ICANN zone-file snapshot AboutUs holds from Mar 27, 2015 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)DNS moved to UltraDNS (Neustar/Vercara)Mar 27, 2015mywedding.com's nameservers moved from DNS Made Easy to UltraDNS (Neustar/Vercara) at some point between Jan 24, 2015 and Mar 27, 2015. Last seen at DNS Made Easy: Jan 24, 2015 (ICANN zone-file snapshot). First seen at UltraDNS (Neustar/Vercara): Mar 27, 2015 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 2 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)Nameservers: Amazon Route 53Nameservers: Amazon Route 53Jun 19, 2018 – Sep 23, 2023Registration records listed Amazon Route 53 nameservers (ns-1005.awsdns-61.net, ns-1353.awsdns-41.org, ns-14.awsdns-01.com…) for mywedding.com from Jun 19, 2018 to Sep 23, 2023.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: MarkMonitorNameservers: MarkMonitorOct 5, 2023 – May 16, 2026Registration records listed MarkMonitor nameservers (ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com…) for mywedding.com from Oct 5, 2023 to May 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)DNS moved to MarkMonitorOct 5, 2023mywedding.com's nameservers moved from Amazon Route 53 to MarkMonitor between Sep 23, 2023 and Oct 5, 2023. Last seen at Amazon Route 53: Sep 23, 2023 (registration record). First seen at MarkMonitor: Oct 5, 2023 (registration record).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: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Certificate
No certificate recorded yet.
200020102020Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (22)
Jul 11, 1998Registration: mywedding.com was registered on Jul 11, 1998.Source: RDAP, fetched Aug 23, 2026
Jun 21, 2006 – Nov 7, 2013AboutUs record: An AboutUs wiki page described mywedding.com from Jun 21, 2006 to Nov 7, 2013 (3 edits).Source: AboutUs wiki archive, 2006–2023
May 17, 2007 – May 16, 2026Registrant: Registration records for mywedding.com are held from May 17, 2007 to May 16, 2026 (575 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 17, 2007 – Apr 11, 2008Zone file: Registration records listed UltraDNS (Neustar/Vercara) nameservers (udns1.ultradns.net) for mywedding.com from May 17, 2007 to Apr 11, 2008.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 15, 2008 – Oct 17, 2013Zone file: Registration records listed DNS Made Easy nameservers (ns0.dnsmadeeasy.com) for mywedding.com from Apr 15, 2008 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)
Apr 15, 2008Zone file: mywedding.com's nameservers moved from UltraDNS (Neustar/Vercara) to DNS Made Easy between Apr 11, 2008 and Apr 15, 2008. Last seen at UltraDNS (Neustar/Vercara): Apr 11, 2008 (registration record). First seen at DNS Made Easy: Apr 15, 2008 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jun 6, 2009Registrant: The registrant name or organization in the registration record changed; first recorded Jun 6, 2009. 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
Sep 10, 2011 – Jun 10, 2014Registrar: Registrar ENOM, INC. (IANA 48) in the WHOIS and RDAP records held for mywedding.com, from Sep 10, 2011 to Jun 10, 2014.Source: WHOIS / RDAP archive (who.is)
Mar 28, 2013Registrant: The registrant name or organization in the registration record changed; first recorded Mar 28, 2013. 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
Oct 18, 2013 – Jan 24, 2015Zone file: DNS Made Easy (ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com…) were the nameservers listed for mywedding.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Jan 24, 2015 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Mar 27, 2015 – Apr 3, 2018Zone file: UltraDNS (Neustar/Vercara) (pdns152.ultradns.biz, pdns152.ultradns.com, pdns152.ultradns.net…) were the nameservers listed for mywedding.com at every ICANN zone-file snapshot AboutUs holds from Mar 27, 2015 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Mar 27, 2015Zone file: mywedding.com's nameservers moved from DNS Made Easy to UltraDNS (Neustar/Vercara) at some point between Jan 24, 2015 and Mar 27, 2015. Last seen at DNS Made Easy: Jan 24, 2015 (ICANN zone-file snapshot). First seen at UltraDNS (Neustar/Vercara): Mar 27, 2015 (ICANN zone-file snapshot). AboutUs holds no nameserver records for the 2 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → ICANN zone-file snapshot)
Jul 20, 2016 – Jul 23, 2018Registrar: Registrar TUCOWS, INC. (IANA 69) in the WHOIS and RDAP records held for mywedding.com, from Jul 20, 2016 to Jul 23, 2018.Source: WHOIS / RDAP archive (who.is)
Jul 20, 2016Registrant: The registrant name or organization in the registration record changed; first recorded Jul 20, 2016. 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
Jun 19, 2018 – Sep 23, 2023Zone file: Registration records listed Amazon Route 53 nameservers (ns-1005.awsdns-61.net, ns-1353.awsdns-41.org, ns-14.awsdns-01.com…) for mywedding.com from Jun 19, 2018 to Sep 23, 2023.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 13, 2018 – Oct 7, 2026Registrar: Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Aug 13, 2018 and most recently on Oct 7, 2026.Source: RDAP, fetched Aug 23, 2026
Jul 26, 2022Registrant: The registrant name or organization in the registration record changed; first recorded Jul 26, 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
Oct 5, 2023 – May 16, 2026Zone file: Registration records listed MarkMonitor nameservers (ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com…) for mywedding.com from Oct 5, 2023 to May 16, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Oct 5, 2023Zone file: mywedding.com's nameservers moved from Amazon Route 53 to MarkMonitor between Sep 23, 2023 and Oct 5, 2023. Last seen at Amazon Route 53: Sep 23, 2023 (registration record). First seen at MarkMonitor: Oct 5, 2023 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jul 14, 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: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com.Source: ICANN CZDS zone file, snapshot Nov 1, 2026
Automated safety checks
DNS (passed)
HTTPS (failed)
Make sure the site responds over HTTPS with a valid certificate.
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 Jul 11, 1998 — 28 years old.
latest result
Registrar on record: MarkMonitor Inc. — unchanged since AboutUs began tracking (Jul 25, 2026).
Authority 46/100— ahead of 46% of the August 2026 scored sampleClear
Why this authority score
46 is a percentile: higher than 46% of sites we score.
How it's calculated
Prominence (Tranco rank #344,928)+5
Verified continuity: 28.3 years (RDAP registration)+11
Security & email hygiene+2
Calibration adjustment (published map)+7
Model score: 25/99 — what these reason lines add up to.
Published Authority (percentile): 46/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.
Recorded HTTPS check did not confirm a valid connection
No MX and no DMARC (mild)
What mywedding.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
Your complete wedding planning guide. Find wedding photographers, wedding reception facilities, wedding ceremony sites, wedding cakes, wedding dresses, and more!
Site history
Dated record — historical facts always carry their date.