Verifying against the live site and live WHOIS/DNS…
Common questions
Is pfsense.org legit or a scam?
pfsense.org was registered Nov 5, 2004 (22 years old), per public registration records. 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 pfsense.org?
Nobody has completed AboutUs's owner verification for pfsense.org. That's true of most sites here — it isn't itself a warning sign.
When was pfsense.org registered?
pfsense.org's registration dates to Nov 5, 2004 (22 years old), per public registration records. Gandi SAS is the registrar on record today.
Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · pfsense.org over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 22 years ago · on AboutUs since 2006 · 1 registrar change since May 14, 2012 · 2 registrant changes since 2012 · last checked Nov 15, 2026.
Registration
RegisteredNov 5, 2004pfsense.org was registered on Nov 5, 2004.Source: RDAP, fetched Nov 7, 2026
AboutUs record
AboutUs wiki pageAboutUs wiki pageJun 21, 2006 – Nov 6, 2013An AboutUs wiki page described pfsense.org from Jun 21, 2006 to Nov 6, 2013 (3 edits).Source: AboutUs wiki archive, 2006–2023Said about itself in 2006
Registrar
eNom, Inc. (R39-LROR)May 14, 2012 – Feb 21, 2014Registrar eNom, Inc. (R39-LROR) in the WHOIS and RDAP records held for pfsense.org, from May 14, 2012 to Feb 21, 2014.Source: WHOIS / RDAP archive (who.is)GANDI SAS
Registrant
Registrant recordsMay 14, 2012 – Jun 18, 2026Registration records for pfsense.org are held from May 14, 2012 to Jun 18, 2026 (139 records). 2 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
Zone file
No nameserver records held, Feb 2014 – Jul 2016Nameservers: NamecheapMay 14, 2012 – Feb 21, 2014Registration records listed Namecheap nameservers (dns1.registrar-servers.com, dns2.registrar-servers.com, dns3.registrar-servers.com…) for pfsense.org from May 14, 2012 to Feb 21, 2014.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
Comodo CA LimitedAug 22, 2011 – Aug 21, 2013Comodo CA Limited issued 2 certificates for pfsense.org from Aug 22, 2011, the latest valid until Aug 21, 2013.Source: Certificate Transparency logs (crt.sh)GlobalSign nv-saAug 21, 2013 – Aug 20, 2014
20052010201520202025Apr ’26← last 12 months, drawn wider
Every dated fact on this lifeline (18)
Nov 5, 2004Registration: pfsense.org was registered on Nov 5, 2004.Source: RDAP, fetched Nov 7, 2026
Jun 21, 2006 – Nov 6, 2013AboutUs record: An AboutUs wiki page described pfsense.org from Jun 21, 2006 to Nov 6, 2013 (3 edits).Source: AboutUs wiki archive, 2006–2023
Jul 1, 2006AboutUs record: “A free firewall based on Packet Filter (pf) and FreeBSD 6.”Source: AboutUs wiki archive, 2006
Aug 22, 2011 – Aug 21, 2013Certificate: Comodo CA Limited issued 2 certificates for pfsense.org from Aug 22, 2011, the latest valid until Aug 21, 2013.Source: Certificate Transparency logs (crt.sh)
May 14, 2012 – Feb 21, 2014Registrar: Registrar eNom, Inc. (R39-LROR) in the WHOIS and RDAP records held for pfsense.org, from May 14, 2012 to Feb 21, 2014.Source: WHOIS / RDAP archive (who.is)
May 14, 2012 – Jun 18, 2026Registrant: Registration records for pfsense.org are held from May 14, 2012 to Jun 18, 2026 (139 records). 2 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.
Jul 1, 2006
“A free firewall based on Packet Filter (pf) and FreeBSD 6.”
Source: AboutUs wiki archive, 2006
Current AboutUs recordJul 3, 2026 – Nov 7, 2026 (latest)Authority and Safety last refreshed Nov 7, 2026.Source: AboutUs checks
GANDI SAS
Jul 19, 2016 – Nov 15, 2026 (latest)
Registrar GANDI SAS (IANA 81) in the registration data recorded, first on Jul 19, 2016 and most recently on Nov 15, 2026.
Source: RDAP, fetched Nov 7, 2026
Registrant changeFeb 7, 2014The registrant name or organization in the registration record changed; first recorded Feb 7, 2014. 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
Registrant changeJul 19, 2016The registrant name or organization in the registration record changed; first recorded Jul 19, 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
2 registrant changes, 2012–2026
Nameservers: netgate.com, pfmechanics.comJul 19, 2016Registration records listed netgate.com, pfmechanics.com nameservers (ns1.netgate.com, ns1.pfmechanics.com, ns2.pfmechanics.com…) for pfsense.org from Jul 19, 2016 to Jul 19, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to netgate.com, pfmechanics.comJul 19, 2016pfsense.org's nameservers moved from Namecheap to netgate.com, pfmechanics.com at some point between Feb 21, 2014 and Jul 19, 2016. Last seen at Namecheap: Feb 21, 2014 (registration record). First seen at netgate.com, pfmechanics.com: Jul 19, 2016 (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: netgate.comNameservers: netgate.comJul 26, 2016 – Jun 18, 2026Registration records listed netgate.com nameservers (ns1.netgate.com, ns2.netgate.com) for pfsense.org from Jul 26, 2016 to Jun 18, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to netgate.comJul 26, 2016pfsense.org's nameservers moved from netgate.com, pfmechanics.com to netgate.com between Jul 19, 2016 and Jul 26, 2016. Last seen at netgate.com, pfmechanics.com: Jul 19, 2016 (registration record). First seen at netgate.com: Jul 26, 2016 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
GlobalSign nv-sa issued 1 certificate for pfsense.org from Aug 21, 2013, the latest valid until Aug 20, 2014.
Source: Certificate Transparency logs (crt.sh)
COMODO CA LimitedCOMODO CA LimitedAug 20, 2014 – Aug 21, 2020COMODO CA Limited issued 3 certificates for pfsense.org from Aug 20, 2014, the latest valid until Aug 21, 2020.Source: Certificate Transparency logs (crt.sh)
Let's EncryptLet's EncryptAug 17, 2020 – Nov 19, 2026 (latest)Let's Encrypt issued 86 certificates for pfsense.org from Aug 17, 2020, the latest valid until Feb 12, 2027. Seen in use on Nov 15, 2026.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader); TLS check, Nov 15, 2026
Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
May 14, 2012 – Feb 21, 2014Zone file: Registration records listed Namecheap nameservers (dns1.registrar-servers.com, dns2.registrar-servers.com, dns3.registrar-servers.com…) for pfsense.org from May 14, 2012 to Feb 21, 2014.Source: From registration records (WHOIS / RDAP archive, who.is)
Aug 21, 2013 – Aug 20, 2014Certificate: GlobalSign nv-sa issued 1 certificate for pfsense.org from Aug 21, 2013, the latest valid until Aug 20, 2014.Source: Certificate Transparency logs (crt.sh)
Feb 7, 2014Registrant: The registrant name or organization in the registration record changed; first recorded Feb 7, 2014. 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
Aug 20, 2014 – Aug 21, 2020Certificate: COMODO CA Limited issued 3 certificates for pfsense.org from Aug 20, 2014, the latest valid until Aug 21, 2020.Source: Certificate Transparency logs (crt.sh)
Jul 19, 2016 – Nov 15, 2026Registrar: Registrar GANDI SAS (IANA 81) in the registration data recorded, first on Jul 19, 2016 and most recently on Nov 15, 2026.Source: RDAP, fetched Nov 7, 2026
Jul 19, 2016Registrant: The registrant name or organization in the registration record changed; first recorded Jul 19, 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
Jul 19, 2016Zone file: Registration records listed netgate.com, pfmechanics.com nameservers (ns1.netgate.com, ns1.pfmechanics.com, ns2.pfmechanics.com…) for pfsense.org from Jul 19, 2016 to Jul 19, 2016.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 19, 2016Zone file: pfsense.org's nameservers moved from Namecheap to netgate.com, pfmechanics.com at some point between Feb 21, 2014 and Jul 19, 2016. Last seen at Namecheap: Feb 21, 2014 (registration record). First seen at netgate.com, pfmechanics.com: Jul 19, 2016 (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)
Jul 26, 2016 – Jun 18, 2026Zone file: Registration records listed netgate.com nameservers (ns1.netgate.com, ns2.netgate.com) for pfsense.org from Jul 26, 2016 to Jun 18, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jul 26, 2016Zone file: pfsense.org's nameservers moved from netgate.com, pfmechanics.com to netgate.com between Jul 19, 2016 and Jul 26, 2016. Last seen at netgate.com, pfmechanics.com: Jul 19, 2016 (registration record). First seen at netgate.com: Jul 26, 2016 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Aug 17, 2020 – Nov 19, 2026Certificate: Let's Encrypt issued 86 certificates for pfsense.org from Aug 17, 2020, the latest valid until Feb 12, 2027. Seen in use on Nov 15, 2026.Source: Certificate Transparency logs (crt.sh + AboutUs's own certificate-log reader); TLS check, Nov 15, 2026
Jul 3, 2026 – Nov 7, 2026AboutUs record: Authority and Safety last refreshed Nov 7, 2026.Source: AboutUs checks
Registered 2004 · site is live · HTTPS valid
Pfsense.org pfSense Open Source Firewall Distribution
A free firewall based on Packet Filter (pf) and FreeBSD 6.
Authority 83/100— ahead of 83% of the August 2026 scored sampleClear
Why this authority score
83 is a percentile: higher than 83% of sites we score.
How it's calculated
Prominence (Tranco rank #14,004)+9
Verified continuity: 22.0 years (RDAP registration)+10
Security & email hygiene+4
Calibration adjustment (published map)+19
Model score: 42/99 — what these reason lines add up to.
Published Authority (percentile): 83/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 11 days ago); 3/3 transport and email checks available (oldest recorded about 11 days ago). This is evidence coverage, not a probability that a website is safe.
What pfsense.org 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
A free firewall based on Packet Filter (pf) and FreeBSD 6.
Site history
Dated record — historical facts always carry their date; self-description below is the 2013 record.
2004
Domain registered (Nov 5, 2004).
2006
First tracked by AboutUs (Jun 21, 2006); profile edited 3 times through 2013.
2013
Self-description at the time:
“Pfsense.org pfSense Open Source Firewall Distribution”