Emitech Corp. — 2 prefixes (MA-L)

A MAC address starting with 00:26:48 or 00:1D:83 belongs to Emitech Corp. (also filed under the name Emitech Corporation), a Taiwan-based registrant holding two separate IEEE MA-L OUI blocks. No verifiable product line, device category, or working vendor website could be found, so beyond "hardware made by this registrant," the device class this identifies stays Unknown.

The cached IEEE registry lists two distinct MA-L assignments for this org: 00:26:48, registered to "Emitech Corp." at No. 156-5A, ChengGong 1st St., Jhubei City, Hsinchu County, Taiwan, and 00:1D:83, registered to "Emitech Corporation" at 2F, No. 7-1, Industry E, Rd. 9, Hsinchu, Taiwan. Both addresses sit in Taiwan's Hsinchu tech-industrial corridor.

Beyond the two standalone OUIs, the same organization name is attributed to two /36 sub-allocations under the shared IEEE CID block 00:50:C2 — 00:50:C2:7C:F0/36 and 00:50:C2:96:50/36. That base block is not Emitech's: the registry shows thousands of unrelated registrants under 00:50:C2:xx, so only the two named /36 slices belong to this vendor, never the 00:50:C2 base itself.

Multiple web searches — the company name, its Hsinchu/Jhubei/ChengGong address terms, a guessed emitech.com.tw domain, and a Taiwan MOEA company-registry lookup (blocked, HTTP 403) — turned up no working vendor site or device documentation. Results instead surfaced unrelated same-named companies (a Massachusetts biotech, a French/Moroccan testing-lab group, a Chinese CNC-parts maker, a Chinese netting exporter), none matching this Hsinchu registrant. No CVE, malware, or botnet association was found for "Emitech" as of an August 2026 search.

IEEE assignment

00:26:48 → Emitech Corp., Jhubei City, Hsinchu County, TW [Confirmed] — the IEEE MA-L registry 002648

IEEE assignment

00:1D:83 → Emitech Corporation, Hsinchu, TW [Confirmed] — the IEEE MA-L registry 001D83

Registry / block size

MA-L (24-bit OUI) x2; no third-party aggregate prefix-count total is published for this vendor [Confirmed] — the IEEE MA-L registry 002648, 001D83

HQ / country

Taiwan; two Hsinchu-area addresses on file (Jhubei City ChengGong 1st St.; Hsinchu Industry E Rd. 9) [Confirmed] — the IEEE MA-L registry 002648, 001D83

Company status

Unknown — no corporate registry or live web presence confirmed [Unknown] — findbiz.nat.gov.tw (Taiwan MOEA lookup returned HTTP 403, could not be queried)

Device types

Unknown — no product documentation found [Unknown]

Notable products

Unknown [Unknown]

Sub-allocations (shared CID 00

50:C2): 00:50:C2:7C:F0/36 and 00:50:C2:96:50/36 attributed to Emitech Corporation; the 00:50:C2 base itself is a shared IEEE CID with thousands of unrelated registrants and must never be attributed to Emitech [Confirmed] — the Wireshark manufacturer database 00:50:C2:7C:F0/36, 00:50:C2:96:50/36

Registration dates

Not published by IEEE for either OUI; no date field exists in the cached registry [Confirmed] — the IEEE MA-L registry 002648, 001D83

Special note

Two registrations under closely related names ("Emitech Corp." vs "Emitech Corporation") at two different Hsinchu-area addresses — plausibly the same entity across two filings, but not confirmed identical [Likely] — the IEEE MA-L registry 002648, 001D83

Related vendors

None confirmed related; several unrelated same-named companies exist elsewhere (Emitech Inc., Fall River MA, biotech; Emitech Group, France/Morocco testing labs; Nanjing Emitech Technology, China; Emitech Industry Co, China) — none correspond to this Taiwan registrant [Confirmed] — https://emitechinc.com/, https://www.emitech-group.com/en, https://www.tendata.com/en/supplier/nanjing-emitech-technology-co-ltd-CHN66bd07537dd6166eb70669071d9a09d5.html, https://www.volza.com/company-profile/emitech-industry-co-limited-16802720/

Security context

No CVE, malware, or botnet association found for "Emitech" as of an August 2026 search [Likely]

Analyst note

Two independent MA-L OUI assignments plus two named /36 sub-allocations under a shared CID indicate an active, multi-registration hardware vendor rather than a single-OUI shell — but no product line, device category, or working website was found, so device-type inference for this vendor stays Unknown [Likely]