Illustrative sample
Brand risk example: a fictional B2B SaaS company
The written findings of a free growth diagnostic on brand risk, shown on Quarrelane Software, a fictional company. Every domain, name and finding is made up.
About this sample
- Quarrelane Software is fictional: no client data is used
- Goal: brand risk
- Public checks only, nothing shared in advance
- Every table holds example data, illustrative
This illustrative sample shows what you receive after a free growth diagnostic on brand risk: the exposure we found from public checks, the top 3 risks, the fixes your team can make now, and what needs a specialist firm. The company, its domains and every finding are fictional.
Illustrative sample
Quarrelane Software is a fictional B2B SaaS company. Its domains end in .example, a top-level name reserved for documentation and examples. No real domain, company or person was checked for this page.
The exposure we found
Quarrelane shared its main domain, two product names and its company social handles. Every check below used public records only; nobody at Quarrelane gave us access to anything.
| Check | What we found | Risk |
|---|---|---|
| Email authentication on quarrelane.example | SPF and DKIM in place; DMARC published at p=none, with reports going to a former agency’s mailbox. | High |
| Lookalike domains | Two recent registrations: quarre1ane.example (the letter l swapped for the digit 1) and quarrelane-billing.example. The second has mail records, so it can send and receive email. | High |
| Domain renewals and ownership | The main domain renews in 23 days. Renewal notices go to the personal address of an employee who has left. | Medium |
| Fake profiles and pages | One LinkedIn profile using the company name and logo with a job title that does not exist at Quarrelane. | Medium |
| Second product domain | Registrar lock on, DMARC at p=reject. | Low |
| Check | What we found | Risk |
|---|---|---|
| Email authentication on quarrelane.example | SPF and DKIM in place; DMARC published at p=none, with reports going to a former agency’s mailbox. | High |
| Lookalike domains | Two recent registrations: quarre1ane.example (the letter l swapped for the digit 1) and quarrelane-billing.example. The second has mail records, so it can send and receive email. | High |
| Domain renewals and ownership | The main domain renews in 23 days. Renewal notices go to the personal address of an employee who has left. | Medium |
| Fake profiles and pages | One LinkedIn profile using the company name and logo with a job title that does not exist at Quarrelane. | Medium |
| Second product domain | Registrar lock on, DMARC at p=reject. | Low |
Example data, illustrative.
Your top 3 risks
- Anyone can send email that claims to come from quarrelane.example. DMARC at p=none states no preference about mail that fails authentication, so receivers decide on their own, and the reports that would show abuse go to a mailbox nobody at Quarrelane reads.
- quarrelane-billing.example can send email. With a billing name and working mail records, it is set up for fake invoices or payment change requests to Quarrelane’s customers.
- The main domain could lapse. If the renewal fails, email and the website stop, and the domain can be registered by someone else once it is released.
The fixes your team can make now
In order. Owners are roles on Quarrelane’s team; none of these needs DGo.
| When | What to do | Owner | Effort |
|---|---|---|---|
| This week | Renew the main domain for several years, move renewal notices to a shared company mailbox and turn on MFA at the registrar. | IT | 1 hour |
| This week | Point DMARC reports to a mailbox the team reads, and confirm every service that sends mail as Quarrelane passes SPF or DKIM. | IT | 2 to 3 hours |
| Week 2 | Tell finance and customer success about quarrelane-billing.example, and remind customers how real invoices and bank changes arrive. | Finance and customer success | 1 hour |
| Week 2 | Report the fake LinkedIn profile with LinkedIn’s own reporting tools, after saving screenshots and the profile link. | Marketing | 30 minutes |
| Weeks 2 to 6 | Move DMARC to p=quarantine, then to p=reject, in stages, once the reports show only your own mail. | IT | 30 minutes a week |
| When | What to do | Owner | Effort |
|---|---|---|---|
| This week | Renew the main domain for several years, move renewal notices to a shared company mailbox and turn on MFA at the registrar. | IT | 1 hour |
| This week | Point DMARC reports to a mailbox the team reads, and confirm every service that sends mail as Quarrelane passes SPF or DKIM. | IT | 2 to 3 hours |
| Week 2 | Tell finance and customer success about quarrelane-billing.example, and remind customers how real invoices and bank changes arrive. | Finance and customer success | 1 hour |
| Week 2 | Report the fake LinkedIn profile with LinkedIn’s own reporting tools, after saving screenshots and the profile link. | Marketing | 30 minutes |
| Weeks 2 to 6 | Move DMARC to p=quarantine, then to p=reject, in stages, once the reports show only your own mail. | IT | 30 minutes a week |
Example data, illustrative.
What needs a specialist firm
quarrelane-billing.example uses the company name and could be used for fraud. If it is, reports to its registrar and host come first. Getting the domain transferred is a legal process: under the UDRP, the trademark holder files a complaint with an approved dispute resolution provider.
Takedowns and incident response
DGo does not do legal takedowns or incident response. Specialist work goes to partners, and we name them in the proposal before you sign.
How a real diagnostic differs
- It checks your own domains, brand names and handles, from public records.
- Nothing to share in advance; a read-only view of your DNS only if you offer it.
- Your top 3 findings and a 30-day fix plan arrive in writing within 2 business days.
- You keep them, whether or not you work with us.
Sources
An illustrative sample written under our Editorial and AI Policy. Quarrelane Software and every figure on this page are fictional.