Verifying against the live site and live WHOIS/DNS…
Common questions
Is masstimes.org 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 masstimes.org?
Nobody has completed AboutUs's owner verification for masstimes.org. 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.
3 of 4 safety checks passed (Oct 29, 2026).
Registered 1997 · site is live · HTTPS valid
MassTimes.org
First, a service to help Catholics with handicaps, migrants, pilgrims, refugees, travelers and workers on the road find a Mass or other worship services.
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 29 years ago · on AboutUs since 2006 · one registrar since Jul 18, 2016 · 2 ownership changes since 2016 · last checked Oct 15, 2026.
Registration
RegisteredOct 25, 1997masstimes.org was registered on Oct 25, 1997.Source: RDAP, fetched Sep 6, 2026
AboutUs record
AboutUs wiki pageJun 21, 2006An AboutUs wiki page described masstimes.org from Jun 21, 2006 to Jun 21, 2006 (1 edit).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJun 22, 2026 – Aug 23, 2026 (latest)
Registrar
Network Solutions, LLCNetwork Solutions, LLCJul 18, 2016 – Oct 29, 2026 (latest)Registrar Network Solutions, LLC (IANA 2) in the registration data recorded, first on Jul 18, 2016 and most recently on Oct 29, 2026.Source: RDAP, fetched Sep 6, 2026
Ownership
Ownership recordsJul 18, 2016 – Jun 9, 2026Registration records for masstimes.org are held from Jul 18, 2016 to Jun 9, 2026 (61 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
Nameservers: zerigo.netJul 18, 2016 – Feb 19, 2017Registration records listed zerigo.net nameservers (a.ns.zerigo.net, b.ns.zerigo.net, c.ns.zerigo.net…) for masstimes.org from Jul 18, 2016 to Feb 19, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)Nameservers: Amazon Route 53
Certificate
Let's EncryptApr 18, 2026 – Oct 29, 2026 (latest)Let's Encrypt issued 9 certificates for masstimes.org from Apr 18, 2026, the latest valid until Jan 22, 2027. Seen in use on Oct 15, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 15, 2026
200020102020Jan ’26Oct ’26← last 12 months, drawn wider
Every dated fact on this lifeline (11)
Oct 25, 1997Registration: masstimes.org was registered on Oct 25, 1997.Source: RDAP, fetched Sep 6, 2026
Jun 21, 2006AboutUs record: An AboutUs wiki page described masstimes.org from Jun 21, 2006 to Jun 21, 2006 (1 edit).Source: AboutUs wiki archive, 2006–2023
Jul 18, 2016 – Oct 29, 2026Registrar: Registrar Network Solutions, LLC (IANA 2) in the registration data recorded, first on Jul 18, 2016 and most recently on Oct 29, 2026.Source: RDAP, fetched Sep 6, 2026
Jul 18, 2016 – Jun 9, 2026Ownership: Registration records for masstimes.org are held from Jul 18, 2016 to Jun 9, 2026 (61 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
Jul 18, 2016 – Feb 19, 2017Zone file: Registration records listed zerigo.net nameservers (a.ns.zerigo.net, b.ns.zerigo.net, c.ns.zerigo.net…) for masstimes.org from Jul 18, 2016 to Feb 19, 2017.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 19, 2017 – Jun 9, 2026
Authority and Safety last refreshed Aug 23, 2026.
Source: AboutUs checks
Ownership change
Aug 26, 2020
The registrant name or organization in the registration record changed; first recorded Aug 26, 2020. Who it changed to is in the full report.
Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Ownership changeSep 16, 2025The registrant name or organization in the registration record changed; first recorded Sep 16, 2025. 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, 2016–2026
Nameservers: Amazon Route 53
Apr 19, 2017 – Jun 9, 2026
Registration records listed Amazon Route 53 nameservers (ns-1263.awsdns-29.org, ns-2001.awsdns-58.co.uk, ns-335.awsdns-41.com…) for masstimes.org from Apr 19, 2017 to Jun 9, 2026.
Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Amazon Route 53Apr 19, 2017masstimes.org's nameservers moved from zerigo.net to Amazon Route 53 at some point between Feb 19, 2017 and Apr 19, 2017. Last seen at zerigo.net: Feb 19, 2017 (registration record). First seen at Amazon Route 53: Apr 19, 2017 (registration record). AboutUs holds no nameserver records for the 59 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)
Zone file: Registration records listed Amazon Route 53 nameservers (ns-1263.awsdns-29.org, ns-2001.awsdns-58.co.uk, ns-335.awsdns-41.com…) for masstimes.org from Apr 19, 2017 to Jun 9, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Apr 19, 2017Zone file: masstimes.org's nameservers moved from zerigo.net to Amazon Route 53 at some point between Feb 19, 2017 and Apr 19, 2017. Last seen at zerigo.net: Feb 19, 2017 (registration record). First seen at Amazon Route 53: Apr 19, 2017 (registration record). AboutUs holds no nameserver records for the 59 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)
Aug 26, 2020Ownership: The registrant name or organization in the registration record changed; first recorded Aug 26, 2020. Who it changed to is in the full report.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Sep 16, 2025Ownership: The registrant name or organization in the registration record changed; first recorded Sep 16, 2025. Who it changed to is in the full report.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
Apr 18, 2026 – Oct 29, 2026Certificate: Let's Encrypt issued 9 certificates for masstimes.org from Apr 18, 2026, the latest valid until Jan 22, 2027. Seen in use on Oct 15, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Oct 15, 2026
Jun 22, 2026 – Aug 23, 2026AboutUs record: Authority and Safety last refreshed Aug 23, 2026.Source: AboutUs checks
Automated safety checks
DNS (passed)
HTTPS (passed)
Page metadata (passed)
Security headers (failed)
Add the HSTS, Content-Security-Policy, and X-Frame-Options response headers.
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 Oct 25, 1997 — 29 years old.
latest result
Registrar on record: Network Solutions, LLC — unchanged since AboutUs began tracking (Sep 6, 2026).
latest result
HTTPS request succeeded for masstimes.org.
checked Oct 3, 2026
The site names MassTimes as the organisation behind it.
checked Oct 3, 2026
The live front page reads as a non-profit, association or religious site that is funded by donations or members.
✓ domain continuity 29 years registered✓ live verified Oct 29, 2026
Safety evidence
No unexpired threat-feed result; name-similarity check available (recorded about 67 days ago); 3/3 transport and email checks available (oldest recorded about 67 days ago). This is evidence coverage, not a probability that a website is safe.
No caution flags in the available scoring observations; this is not a complete safety assessment