Fiery
Sources & updates
How this name was decided
the site's published name — stated on fierysf.com, inspections.myhealthdepartment.com, facebook.com
Profile sources
- Facebookdeclared on fierysf.com
- Last observed
- Oct 18, 2026, 4:16 PM UTCCurrent
- Record last changed
- Oct 18, 2026, 4:16 PM UTC
- Observations
- 190
- Sources read
- 27 of 27
Legal Entities & Relationships
FIERY HOT POT AND GRILL LLCLicensed operator of 1 of its locations
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 nameFiery
Published by the company · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/careers → declared og:site_name
- First observed
- Oct 18, 2026, 4:15 PM UTC
- Read from
- https://www.fierysf.com
- Declared languageen-US
Published by the company · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/
- First observed
- Oct 18, 2026, 4:15 PM UTC
- Read from
- https://www.fierysf.com
- Canonical URLhttps://www.fierysf.com
Published by the company · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/
- First observed
- Oct 18, 2026, 4:15 PM UTC
- Read from
- https://www.fierysf.com
Directly observed · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/ → image inside the header's link to the site root
- First observed
- Oct 18, 2026, 4:15 PM UTC
- Read from
- https://www.fierysf.com
Published by the company · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/
- Read from
- https://www.fierysf.com
Fiery Employees & Ownership
People extraction status: People pages read, no person named with a role: 8 of the site's pages read, 4 named people held as candidates
No confirmed people are currently attached to this site.
4 people not confirmed
YIU K TAI
MANAGING MEMBER · filed_party
register_party_kind_unstated
Source not recorded · confirmed Oct 18, 2026, 4:15 PM UTC- Observed via
- https://www.abc.ca.gov/wp-content/uploads/DailyExport-CSV.zip → Filed party of unstated kind on the authority's record of the operating entity, in the role it files
PANSY FONG QUAN
MANAGING MEMBER · filed_party
register_party_kind_unstated
Source not recorded · confirmed Oct 18, 2026, 4:15 PM UTC- Observed via
- https://www.abc.ca.gov/wp-content/uploads/DailyExport-CSV.zip → Filed party of unstated kind on the authority's record of the operating entity, in the role it files
HOI WOOD LEE
MANAGING MEMBER · filed_party
register_party_kind_unstated
Source not recorded · confirmed Oct 18, 2026, 4:15 PM UTC- Observed via
- https://www.abc.ca.gov/wp-content/uploads/DailyExport-CSV.zip → Filed party of unstated kind on the authority's record of the operating entity, in the role it files
JENNY KAM
MANAGING MEMBER · filed_party
register_party_kind_unstated
Source not recorded · confirmed Oct 18, 2026, 4:15 PM UTC- Observed via
- https://www.abc.ca.gov/wp-content/uploads/DailyExport-CSV.zip → Filed party of unstated kind on the authority's record of the operating entity, in the role it files
Job Postings
- Careers page publishedhttps://www.fierysf.com/careers
Directly observed · confirmed Oct 18, 2026, 4:15 PM UTC
- Observed via
- https://www.fierysf.com/careers → read — no schema.org JobPosting declared on it, and no ATS board observed in this run
- First observed
- Oct 18, 2026, 4:15 PM UTC
- Read from
- https://www.fierysf.com
- Careers page publishedhttps://docs.google.com/forms/d/e/1FAIpQLSdRsm11sC3L9LiQPiDCxhwCJZUUUhweqrZG7Phq0Nm4auv-rw/viewform?usp=sf_link
Directly observed
- Observed via
- https://accounts.google.com/v3/signin/identifier?continue=https://docs.google.com/forms/d/e/1FAIpQLSdRsm11sC3L9LiQPiDCxhwCJZUUUhweqrZG7Phq0Nm4auv-rw/viewform?usp%3Dsf_link&followup=https://docs.google.com/forms/d/e/1FAIpQLSdRsm11sC3L9LiQPiDCxhwCJZUUUhweqrZG7Phq0Nm4auv-rw/viewform?usp%3Dsf_link<mpl=forms&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S1781308406:1792340138767178 → the careers link the site labels, on another host; read — it answered with this page, and no opening was read from it
- Read from
- https://accounts.google.com
- Hiring statusno open role: careers page read, no roles listed (2 pages); 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
- Observed via
- https://www.fierysf.com/careers → https://accounts.google.com/v3/signin/identifier?continue=https://docs.google.com/forms/d/e/1FAIpQLSdRsm11sC3L9LiQPiDCxhwCJZUUUhweqrZG7Phq0Nm4auv-rw/viewform?usp%3Dsf_link&followup=https://docs.google.com/forms/d/e/1FAIpQLSdRsm11sC3L9LiQPiDCxhwCJZUUUhweqrZG7Phq0Nm4auv-rw/viewform?usp%3Dsf_link<mpl=forms&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S1781308406:1792340138767178
- Read from
- https://www.fierysf.com
Contact Information
6282801776
(628) 280-1776
- Observed via
- https://www.fierysf.com/
- First observed
- Oct 18, 2026, 4:15 PM UTC
Locations
Where is Fiery located?
1 known location
San Francisco2333 Irving Street, CA, 94122, US
Website & Digital Technology
What powers Fiery's website?
Appears to use Squarespace.
Who manages Fiery's domain and DNS?
fierysf.com was first registered on December 22, 2019. Its registrar is Tucows Domains Inc..
What web infrastructure does Fiery use?
Protocols: TLS 1.3 and HTTP/2.
How is Fiery's website secured?
HTTPS certificate: Let's Encrypt, expires November 24, 2026. The nosniff security header is enabled.
Does Fiery use DNSSEC?
DNSSEC was not enabled when observed.
What marketing and analytics tools does Fiery's website use?
Google Tag Manager (tag management).
View technology, DNS, network and security evidence
More website details
More website details
View mail records and evidence
Mail records: Nothing observed in this category.
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.
