Firehouse Restaurant
Sources & updates
How this name was decided
the site's published name — stated on firehousepdx.com
- Last observed
- Oct 18, 2026, 5:07 PM UTCCurrent
- Record last changed
- Oct 18, 2026, 5:07 PM UTC
- Observations
- 611
- Sources read
- 27 of 27
Legal Entities & Relationships
CARSON MANAGEMENT INCLicensed operator of 1 of its locations
data.oregon.gov
Legal entities
CARSON MANAGEMENT, INC. Licensed operator of 1 of its locations · OR · OR SOS 52308492
- Type
- DOMESTIC BUSINESS CORPORATION
- Filed
- May 27, 2008
- Premises
- 1 licensed premises of this record
Parties as filed
- JOEL CARSON (REGISTERED AGENT)
The authority's own record of the operating entity, reached by searching its register for the licence-proven operator's exact legal name and keeping only the same registration; owners and titles are as filed, not a current cap table.
View registration recordPublished by a third-party source · confirmed Oct 18, 2026, 5:07 PM UTC
- Observed via
- https://data.oregon.gov/resource/tckn-sxa6.json?%24limit=100&%24offset=0&%24order=registry_date+DESC%2C%3Aid&%24where=UPPER%28business_name%29+IN+%28%27CARSON+MANAGEMENT+INC%27%2C%27CARSON+MANAGEMENT%2C+INC%27%2C%27CARSON+MANAGEMENT+INC.%27%2C%27CARSON+MANAGEMENT%2C+INC.%27%2C%27CARSON+MANAGEMENT+INCORPORATED%27%2C%27CARSON+MANAGEMENT%2C+INCORPORATED%27%29 → licence-proven operator CARSON MANAGEMENT INC on https://data.oregon.gov/resource/srxe-qkm2.json?%24limit=100&%24offset=0&%24order=license_expires+DESC%2C%3Aid&%24where=%28UPPER%28trade_name%29%3D%27FIREHOUSE+RESTAURANT%27+OR+%28%28UPPER%28physical_address%29+LIKE+%27711+%25%27+OR+UPPER%28physical_address%29+LIKE+%27711-%25%27+OR+UPPER%28physical_address%29+LIKE+%27%25-711+%25%27%29+AND+%28UPPER%28physical_address%29+LIKE+%27%25DEKUM%25%27+OR+UPPER%28physical_address%29+LIKE+%27%25DE+KUM%25%27%29%29%29+AND+%28UPPER%28city%29%3D%27PORTLAND%27%29
- About
- CARSON MANAGEMENT INC, the licensed operator of its premises
- Read from
- https://data.oregon.gov
- Interpreted by rule
- legal-entities/1
- Evidence ID
- legal-entity:1d43182205c6a75f1f0b2a68
All published fields
- Scope
- The authority's own record of the operating entity, reached by searching its register for the licence-proven operator's exact legal name and keeping only the same registration; owners and titles are as filed, not a current cap table.
- Reached
- legal_name_search
- Premises
- 14ac645ff67ba9b7cee84b1f6a79333f004d80ac5e73468cafc46349520e8f94
- Legal Name
- CARSON MANAGEMENT, INC.
- Jurisdiction
- OR
- Registration
- Kind
- business_license
- Type
- DOMESTIC BUSINESS CORPORATION
- Number
- 52308492
- Parties
- Kind
- person
- Name
- JOEL CARSON
- Role
- REGISTERED AGENT
- Licensee
- CARSON MANAGEMENT, INC.
- Authority
- OR_SOS
- Source id
- or_sos_business
- Issued date
- 2008-05-27
- Observed at
- 2026-10-18T17:07:21.859457306Z
- Jurisdiction
- OR
Relationship evidence
Identity revision 1, last changed
- a declared affiliated site is a relationship the publisher states, not common ownership
- a declared provider account (gift cards, hiring, ordering) is a service relationship, not an affiliation
- a register party at the business's premises is a candidate operator until the Place and legal resolvers bind it
- a licensed operator of the business's premises operates those locations; it is not thereby the brand's owner
- an employer a job board names on the openings posts them; it is not thereby the owner or the operator
- an app's store seller or developer publishes the app; neither is thereby the restaurant's owner
- a menu that names a producer names it; it is not a supply contract, a volume or an exclusivity
- a mail or DMARC service domain in DNS is a technical service relationship, not an affiliation
- a group the site says it is part of is a public affiliation; the equity chain and buying rights are separate questions
- an organization that posts the openings, sells the app or holds a program account shares services with the business; that is not affiliation or ownership
- Published nameFirehouse Restaurant
Published by the company · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/contact → declared og:site_name
- First observed
- Oct 18, 2026, 5:06 PM UTC
- Read from
- https://firehousepdx.com
- Declared languageen-US
Published by the company · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/
- First observed
- Oct 18, 2026, 5:06 PM UTC
- Read from
- https://firehousepdx.com
- Canonical URLhttps://firehousepdx.com
Published by the company · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/
- First observed
- Oct 18, 2026, 5:06 PM UTC
- Read from
- https://firehousepdx.com
- Site icon
Published by the company · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/
- Read from
- https://firehousepdx.com
Firehouse Restaurant Employees & Ownership
The latest people collection is incomplete. Previously confirmed people remain available with their original dates.
JOEL CARSONREGISTERED AGENTper the register
Roles
- REGISTERED AGENT · CARSON MANAGEMENT, INC. · filed partyhttps://data.oregon.gov/resource/tckn-sxa6.json?%24limit=100&%24offset=0&%24order=registry_date+DESC%2C%3Aid&%24where=UPPER%28business_name%29+IN+%28%27CARSON+MANAGEMENT+INC%27%2C%27CARSON+MANAGEMENT%2C+INC%27%2C%27CARSON+MANAGEMENT+INC.%27%2C%27CARSON+MANAGEMENT%2C+INC.%27%2C%27CARSON+MANAGEMENT+INCORPORATED%27%2C%27CARSON+MANAGEMENT%2C+INCORPORATED%27%29
Stated by 1 source
- https://data.oregon.gov/resource/tckn-sxa6.json?%24limit=100&%24offset=0&%24order=registry_date+DESC%2C%3Aid&%24where=UPPER%28business_name%29+IN+%28%27CARSON+MANAGEMENT+INC%27%2C%27CARSON+MANAGEMENT%2C+INC%27%2C%27CARSON+MANAGEMENT+INC.%27%2C%27CARSON+MANAGEMENT%2C+INC.%27%2C%27CARSON+MANAGEMENT+INCORPORATED%27%2C%27CARSON+MANAGEMENT%2C+INCORPORATED%27%29 · Named as a person on the authority's record of the operating entity, in the role it files · REGISTERED AGENT
Published by a third-party source · confirmed Oct 18, 2026, 5:07 PM UTC
- First observed
- Oct 18, 2026, 5:07 PM UTC
Job Postings
- Hiring statusno open role: no careers page or job board found; LinkedIn Jobs not searched: the site links no LinkedIn company of its own to read postings by; Indeed and ZipRecruiter not searched
Derived from observations
Contact Information
Emails
info@firehousepdx.com
info@firehousepdx.com
Directly observed · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/location → printed in page text, not marked up → role address by local-part convention (RFC 2142)
- First observed
- Oct 18, 2026, 5:06 PM UTC
Contact forms
https://firehousepdx.com/contact
Directly observed · confirmed Oct 18, 2026, 5:07 PM UTC
- Observed via
- https://firehousepdx.com/contact → form headed "Questions? Comments? Submit the form below and someone will get back to you shortly." → submits to https://firehousepdx.com/contact → purpose: contact (a way to reply and a free-text field)
- First observed
- Oct 18, 2026, 5:07 PM UTC
https://firehousepdx.com/contact
Directly observed · confirmed Oct 18, 2026, 5:06 PM UTC
- Observed via
- https://firehousepdx.com/contact → form headed "Subscribe" → submits to https://firehousepdx.com/contact → purpose: newsletter (a lone email input)
- First observed
- Oct 18, 2026, 5:06 PM UTC
https://firehousepdx.com/private-events
Directly observed · confirmed Oct 18, 2026, 5:07 PM UTC
- Observed via
- https://firehousepdx.com/private-events → form headed "Firehouse Restaurant" → submits to https://firehousepdx.com/private-events → purpose: private_dining_inquiry (its page names it)
- First observed
- Oct 18, 2026, 5:07 PM UTC
Locations
Where is Firehouse Restaurant located?
1 known location
Portland711 NE Dekum Street, OR, 97211, US
Website & Digital Technology
What powers Firehouse Restaurant's website?
Appears to use Squarespace.
Who manages Firehouse Restaurant's domain and DNS?
firehousepdx.com was first registered on January 2, 2008. Its registrar is GoDaddy.com, LLC, and GoDaddy manages its DNS.
What web infrastructure does Firehouse Restaurant use?
Protocols: TLS 1.3 and HTTP/2.
How is Firehouse Restaurant's website secured?
HTTPS certificate: Let's Encrypt, expires November 19, 2026. The nosniff security header is enabled.
Does Firehouse Restaurant use DNSSEC?
DNSSEC was not enabled when observed.
View technology, DNS, network and security evidence
Email & Mail Infrastructure
Who handles Firehouse Restaurant's incoming email?
Incoming email is routed through Microsoft 365 / Exchange Online Protection.
Which services can send email for Firehouse Restaurant's domain?
SPF authorizes secureserver.net (GoDaddy).
Does Firehouse Restaurant publish SPF and DMARC?
SPF is configured with a hard fail (-all).
View mail records and evidence
More website details
More website details
Apps, Loyalty & Guest Technology
View apps, provider accounts and technical evidence
App store details: Nothing observed in this category.
Publisher files
Nothing observed in this category.
Feeds
Nothing observed in this category.
GitHub
Nothing observed in this category.
Additional site intelligence
Useful site-graph evidence is available on demand instead of being pre-rendered into every company profile.