Control Passport for sahab-cafe.example
A dated snapshot of public records, not a warranty or legal opinion.
Public records read on 16 November 2026, 09:30 UTC.
Verdict
Public records for sahab-cafe.example point to other parties for the main pieces. Nothing seen here shows the business holding them.
What you appear to control
Nothing in this group.
What someone else appears to control
- Domain registration
The registration record at Example Registrar Ltd lists a contact address at nujoomweb.example, not at your domain.
- Email
Mail is handled by Google Workspace, and the SPF record also lets nujoomweb.example send for you. The registration record lists a contact at that same domain, which may mean that party set it up; confirm it with the owner.
What public records cannot settle
- DNS
DNS runs on nameservers at dns-reseller.example. Public records cannot show whether that domain is yours, a provider's or another party's, so confirm it.
- Website hosting
The website appears to be hosted by ExampleHost. Whose account it is cannot be seen.
- Website platform
The site appears to run on WordPress. Who holds the admin login cannot be seen.
- Website certificate
The certificate from Let's Encrypt ends on 1 December 2026. Renewal runs wherever the site is hosted.
Platform and third party services
| Name | Category | Evidence |
|---|---|---|
| Example Registrar Ltd | Registrar | Seen in public records |
| dns-reseller.example | DNS host | Seen in public records |
| ExampleHost | Website hosting | Inferred |
| WordPress | Website platform | Inferred |
| Google Workspace | Seen in public records | |
| nujoomweb.example | Allowed mail sender | Seen in public records |
| Let's Encrypt | Certificate issuer | Seen in public records |
| Google Search Console | Site ownership verification | Seen in public records |
| Meta Business | Site ownership verification | Seen in public records |
Single points of failure
Ranked from the most urgent. Each line says how sure this passport can be.
- Who holds the registrar login is not public
Whoever holds the account at Example Registrar Ltd can renew the domain, move it or let it lapse. Public records cannot show who that is. Check that you can sign in yourself.
- The domain is registered with another party's email
The registration record lists a contact address at nujoomweb.example, which is not your domain. Renewal notices and transfer approvals go to that address.
- Who runs your DNS servers is not confirmed
The nameservers are on dns-reseller.example, a domain this passport cannot tie to you or to a known provider. Whoever runs them can point your website and email anywhere. Confirm that dns-reseller.example belongs to the business or to a provider it pays.
- The website certificate expires soon
The certificate from Let's Encrypt ends on 1 December 2026. Days left: 14. If it is not renewed, browsers warn visitors away. So little time left can mean automatic renewal has stopped.
- Who administers your mail is not public
Mail is handled by Google Workspace. Public records cannot show who holds the administrator login. Without it you cannot add staff, reset passwords or export mail.
- Check a sender that may send mail as you
The SPF record lets servers listed under _spf.nujoomweb.example send mail for your domain. Confirm that the business still uses that sender. If it does not, remove _spf.nujoomweb.example from the SPF record.
- Who holds the hosting account is not public
Public records cannot show who holds the hosting account for sahab-cafe.example. Hosting company: ExampleHost. That account holds the site files, the database and the backups.
- Who holds the website admin login is not public
The site appears to run on WordPress. Ask for an administrator account in the business name, and remove accounts of people who have left.
- No DMARC record
Without DMARC, receiving mail services get no instruction from you about forged mail that uses your domain, and you get no reports about it.
- All nameservers are with one provider
Every nameserver belongs to dns-reseller.example. If that service fails or closes the account, the domain stops working.
Recovery plan
Work through these in order. The registrar comes first, because whoever controls the domain can change everything else.
- Step 1: write to Example Registrar Ltd
Where to write: https://registrar.example
What to attach:
- A business registration or trade licence document
- Photo ID of the person signing the request
- Any receipt or statement showing the business paid for the domain
- Earlier emails or invoices that link the business, the developer and the domain
- This passport, as a dated record of what public data showed
- Step 2: write to dns-reseller.example
No public contact was found. Use the support page of dns-reseller.example.
What to attach:
- A business registration or trade licence document
- Photo ID of the person signing the request
- A signed letter from the business that authorises you to act for it
- This passport, as a dated record of what public data showed
- Step 3: write to ExampleHost
Where to write: https://examplehost.example
What to attach:
- A business registration or trade licence document
- Photo ID of the person signing the request
- Any receipt or statement showing the business paid for hosting
- This passport, as a dated record of what public data showed
- Step 4: write to Google Workspace
Where to write: https://workspace.google.com
What to attach:
- Readiness to add a DNS record the provider gives you, to prove control of the domain
- A business registration or trade licence document
- Photo ID of the person signing the request
- This passport, as a dated record of what public data showed
Handover checklist for the next developer
Hand this list to the next developer. Ticked items already look right in public records; the rest need a login to check.
| Item | Status |
|---|---|
| The registrar account is in the business name and the owner can sign in. | Check with a login |
| The registrant contact uses an address the business controls. | To do |
| Two step sign in is on for the registrar account. | Check with a login |
| Automatic renewal is on, paid by a method the business owns. | Check with a login |
| The transfer lock is on. | Looks done in public records |
| The business has its own login to the DNS host. | Check with a login |
| A full export of the DNS records is saved where the business can reach it. | Check with a login |
| The hosting account is in the business name, or the business has an owner level login. | Check with a login |
| The business has an administrator login to the website. | Check with a login |
| A recent backup of the site files and database is held by the business. | Check with a login |
| The business holds an administrator login for mail. | Check with a login |
| Recovery phone numbers and addresses on the mail and registrar accounts belong to the business. | Check with a login |
| A DMARC record is published, starting with a monitoring policy. | To do |
| The SPF record lists only senders the business uses today. | To do |
| Certificate renewal is automatic and has been tested. | To do |
| Analytics, search console and social media verifications are held by business accounts. | Check with a login |
| Former developers and staff no longer have logins or API keys. | To do |
| All logins are kept in a password manager the business owns. | Check with a login |
| The renewal calendar from this passport is in the owner's calendar. | To do |
| A fresh passport is run after the handover to see the changes in public records. | To do |
Renewal calendar
The file renewals.ics adds these dates to any calendar app, with reminders before each one.
- Website certificate1 December 2026
- Domain registration4 March 2027
Free check
Free check for sahab-cafe.example
- No flagDomain expiry
The domain does not expire in the next 60 days. Days left: 108.
- Needs a lookWho the domain is registered to
The registrant contact uses an address on another domain.
- Needs a lookProtection against forged mail (DMARC)
No DMARC record is published.
Integrity
SHA-256 of passport.json
79520dcd933633b2bc7ab698119c20f6836cd6ae113fa24a2f52bb6825b11b64
Snapshot time (UTC): 2026-11-16T09:30:00Z
To check that this PDF matches its data file, compute the SHA-256 of passport.json and compare it with the value above.