Verifying against the live site and live WHOIS/DNS…
Common questions
Is lawnseed.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 lawnseed.com?
Nobody has completed AboutUs's owner verification for lawnseed.com. That's true of most sites here — it isn't itself a warning sign.
Checked in the last 30 daysOlder, dated recordFrom registration records
On AboutUs since 2006 · 2 registrar changes since May 15, 2009 · 2 ownership changes since 2009 · last checked Sep 28, 2026.
Registration
No registration date on file yet. AboutUs reads it from RDAP when the site is checked.
AboutUs record
AboutUs wiki pageJun 20, 2006 – Jan 12, 2008An AboutUs wiki page described lawnseed.com from Jun 20, 2006 to Jan 12, 2008 (3 edits).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJun 22, 2026 – Aug 17, 2026 (latest)Authority and Safety last refreshed Aug 17, 2026.Source: AboutUs checks
Registrar
Register.comMay 15, 2009 – Jul 11, 2012Registrar Register.com in the WHOIS and RDAP records held for lawnseed.com, from May 15, 2009 to Jul 11, 2012.Source: WHOIS / RDAP archive (who.is)Domain.com, LLCAug 20, 2016 – Jun 22, 2017Registrar Domain.com, LLC (IANA 886) in the WHOIS and RDAP records held for lawnseed.com, from Aug 20, 2016 to Jun 22, 2017.
Ownership
Ownership recordsMay 15, 2009 – Jun 9, 2026Registration records for lawnseed.com are held from May 15, 2009 to Jun 9, 2026 (72 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Zone file
No nameserver records held, Sep 2011 – Oct 2013No nameserver records held, Feb 2025 – Jun 2026Nameservers: siteprotect.comMay 15, 2009 – Sep 12, 2011Registration records listed siteprotect.com nameservers (ns.siteprotect.com, ns2.siteprotect.com) for lawnseed.com from May 15, 2009 to Sep 12, 2011.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
No certificate recorded yet.
2010201520202025Jan ’26← last 12 months, drawn wider
Every dated fact on this lifeline (15)
Jun 20, 2006 – Jan 12, 2008AboutUs record: An AboutUs wiki page described lawnseed.com from Jun 20, 2006 to Jan 12, 2008 (3 edits).Source: AboutUs wiki archive, 2006–2023
May 15, 2009 – Jul 11, 2012Registrar: Registrar Register.com in the WHOIS and RDAP records held for lawnseed.com, from May 15, 2009 to Jul 11, 2012.Source: WHOIS / RDAP archive (who.is)
May 15, 2009 – Jun 9, 2026Ownership: Registration records for lawnseed.com are held from May 15, 2009 to Jun 9, 2026 (72 records). 2 changes of registrant name or organization are marked. Privacy-service and redaction changes are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
May 15, 2009 – Sep 12, 2011Zone file: Registration records listed siteprotect.com nameservers (ns.siteprotect.com, ns2.siteprotect.com) for lawnseed.com from May 15, 2009 to Sep 12, 2011.Source: From registration records (WHOIS / RDAP archive, who.is)
Oct 18, 2013 – Apr 3, 2018Zone file: ipage.com (ns1.ipage.com, ns2.ipage.com) were the nameservers listed for lawnseed.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Source: WHOIS / RDAP archive (who.is)
Amazon Registrar, Inc.Amazon Registrar, Inc.Aug 20, 2017 – Sep 7, 2026 (latest)Registrar Amazon Registrar, Inc. (IANA 468) in the registration data recorded, first on Aug 20, 2017 and most recently on Sep 7, 2026.Source: RDAP, fetched Jun 22, 2026
Ownership change
Aug 20, 2016
The registrant name or organization in the registration record changed; first recorded Aug 20, 2016. Who it changed to is in the full report.
Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Ownership changeAug 20, 2017The registrant name or organization in the registration record changed; first recorded Aug 20, 2017. Who it changed to is in the full report.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
2 ownership changes, 2009–2026
Nameservers: ipage.com
Nameservers: ipage.comOct 18, 2013 – Apr 3, 2018ipage.com (ns1.ipage.com, ns2.ipage.com) were the nameservers listed for lawnseed.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
DNS moved to ipage.comOct 18, 2013lawnseed.com's nameservers moved from siteprotect.com to ipage.com at some point between Sep 12, 2011 and Oct 18, 2013. Last seen at siteprotect.com: Sep 12, 2011 (registration record). First seen at ipage.com: Oct 18, 2013 (ICANN zone-file snapshot). 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 → ICANN zone-file snapshot)
Nameservers: ipage.comNameservers: ipage.comApr 4, 2018 – Feb 26, 2025Registration records listed ipage.com nameservers (ns1.ipage.com, ns2.ipage.com) for lawnseed.com from Apr 4, 2018 to Feb 26, 2025. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: Amazon Route 53Jun 9, 2026Registration records listed Amazon Route 53 nameservers (ns-1171.awsdns-18.org, ns-1643.awsdns-13.co.uk, ns-494.awsdns-61.com…) for lawnseed.com from Jun 9, 2026 to Jun 9, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Amazon Route 53Jun 9, 2026lawnseed.com's nameservers moved from ipage.com to Amazon Route 53 at some point between Feb 26, 2025 and Jun 9, 2026. Last seen at ipage.com: Feb 26, 2025 (registration record). First seen at Amazon Route 53: Jun 9, 2026 (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 – Sep 28, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Sep 28, 2026. Nameservers on Sep 28, 2026: ns-1171.awsdns-18.org, ns-1643.awsdns-13.co.uk, ns-494.awsdns-61.com, ns-533.awsdns-02.net.Source: ICANN CZDS zone file, snapshot Sep 28, 2026
Oct 18, 2013
Zone file: lawnseed.com's nameservers moved from siteprotect.com to ipage.com at some point between Sep 12, 2011 and Oct 18, 2013. Last seen at siteprotect.com: Sep 12, 2011 (registration record). First seen at ipage.com: Oct 18, 2013 (ICANN zone-file snapshot). 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 → ICANN zone-file snapshot)
Aug 20, 2016 – Jun 22, 2017Registrar: Registrar Domain.com, LLC (IANA 886) in the WHOIS and RDAP records held for lawnseed.com, from Aug 20, 2016 to Jun 22, 2017.Source: WHOIS / RDAP archive (who.is)
Aug 20, 2016Ownership: The registrant name or organization in the registration record changed; first recorded Aug 20, 2016. Who it changed to is in the full report.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Aug 20, 2017 – Sep 7, 2026Registrar: Registrar Amazon Registrar, Inc. (IANA 468) in the registration data recorded, first on Aug 20, 2017 and most recently on Sep 7, 2026.Source: RDAP, fetched Jun 22, 2026
Aug 20, 2017Ownership: The registrant name or organization in the registration record changed; first recorded Aug 20, 2017. Who it changed to is in the full report.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 4, 2018 – Feb 26, 2025Zone file: Registration records listed ipage.com nameservers (ns1.ipage.com, ns2.ipage.com) for lawnseed.com from Apr 4, 2018 to Feb 26, 2025. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 9, 2026Zone file: Registration records listed Amazon Route 53 nameservers (ns-1171.awsdns-18.org, ns-1643.awsdns-13.co.uk, ns-494.awsdns-61.com…) for lawnseed.com from Jun 9, 2026 to Jun 9, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 9, 2026Zone file: lawnseed.com's nameservers moved from ipage.com to Amazon Route 53 at some point between Feb 26, 2025 and Jun 9, 2026. Last seen at ipage.com: Feb 26, 2025 (registration record). First seen at Amazon Route 53: Jun 9, 2026 (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)
Jun 22, 2026 – Aug 17, 2026AboutUs record: Authority and Safety last refreshed Aug 17, 2026.Source: AboutUs checks
Sep 8, 2026 – Sep 28, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Sep 28, 2026. Nameservers on Sep 28, 2026: ns-1171.awsdns-18.org, ns-1643.awsdns-13.co.uk, ns-494.awsdns-61.com, ns-533.awsdns-02.net.Source: ICANN CZDS zone file, snapshot Sep 28, 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 Dec 5, 1997 — 28 years old.
latest result
Registrar on record: Amazon Registrar, Inc. — unchanged since AboutUs began tracking (Sep 6, 2026).
We withhold an authority number until independent evidence (global rank, link-graph presence) has accrued. The facts we do have about this site are shown below — we'd rather say “not enough signals yet” than invent a low score.
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)
Site history
Dated record — historical facts always carry their date.