Heraldry and the marks
Why a security portfolio carries a coat of arms
Two marks do two different jobs. The radar is operational. It sits in the header on every page, sweeps when you rest on it, and stands for the work: watching, detecting, resolving. The coat of arms is ceremonial. It appears once, at the gateway, and then steps aside.
The name is a place before it is a family. It comes from the Old English welle and the Old Norse brunnr, a well by a stream, and it is already written down in the Domesday Book of 1086 as Wellebrune in Lincolnshire and Walebruna in Norfolk. The Lincolnshire line held the manor of Welbourn. Hugh de Welleburn turns up in the Hundred Rolls of 1273, Robert Walebrun in the Sussex subsidy rolls of 1296, and the spelling keeps moving for another three hundred years before it settles.
What survives after that is a scatter of people rather than a tidy line. Thomas Welbourne, a schoolmaster, was executed at York in 1605 for his faith and beatified in 1929. Another Thomas sat in the Virginia House of Burgesses from 1699 until his death in 1702, three generations after the first Welbournes crossed in the 1650s. Elijah Welbourne landed in South Australia in 1851, aged twenty five. I make no claim to descend from any of them in particular. That is the honest position with a name this old, and it is the more interesting one.
So the arms are here for what they represent rather than as a pedigree. An armorial achievement is an identity that is inherited and defended rather than bought, which is a fair thing to open a defensive security portfolio with and an easy thing to over-use. The gateway is the only place it renders at full size. Past it, you get the plain operational system that runs the rest of this site.
The arms are drawn twice, in colour and as an engraving, and the theme decides which one you get. Both are pre-rendered to WebP at three widths, because a ceremonial entrance that costs a second of loading is not ceremonial, it is slow.
View the ceremonial entrance ↗