marmite.co.uk
Observed Aug 11, 2026, 02:18 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.
marmite.co.uk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting marmite.co.uk under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.
Watch marmite.co.uk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google (SPF sender)
Google Search ConsoleSteady. No change on record for marmite.co.uk in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 1
20.238.208.21
MX 10
30mail.marmite.co.uk40mail.forum.marmite.co.uk10mx1.unilever-uk.trclient.com20mx2.unilever-uk.trclient.com100relay2.unilever.com100relay3.unilever.com100relay21.unilever.com100relay22.unilever.com100relay23.unilever.com100relay1.unilever.com
TXT 5
v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com include:marmite.co.uk include:unilever-uk.trclient.com include:unilever.com -allspf2.0/pra include:unilever-uk.trclient.com -all047C-E1BB-834E-9411-BF1C-CEA9-F775-9C90google-site-verification=bm027NFe0QdVVybOiBsPxlK_yA3yBMl0mEJ7FaDds2ggoogle-site-verification=blxT6HrTxjXWRdhnuQOh5u6ZqtcObSmFWWpevWGvjcc
NS 4
ns1-44.azure-dns.comns2-44.azure-dns.netns3-44.azure-dns.orgns4-44.azure-dns.info
SOA 1
ns1-44.azure-dns.com postmaster.dns04.unilever.com
MCP_RECORDS 1
v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all
DMARC_RECORDS 1
v=DMARC1; rua=mailto:92dea1233e27591@rep.dmarcanalyzer.com; ruf=mailto:92dea1233e27591@for.dmarcanalyzer.com; p=none; sp=none; fo=1;
BIMI_RECORDS 1
v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all
MTA_STS_RECORDS 1
v=spf1 mx a ptr include:servers.mcsv.net include:_spf.google.com include:amazonses.com include:amazonaws.com include:mail.dms.unileverservices.com -all
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
webredirect11.unilever.com |
C=CA, O=Entrust Limited, CN=Entrust OV TLS Issuing RSA CA 2 | Fri, 29 Jan 2027 23:59:59 +0000 |
USERTrust RSA Certification Authority |
C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority | Mon, 18 Jan 2038 23:59:59 +0000 |
Sectigo Public Server Authentication Root R46 |
C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority | Mon, 18 Jan 2038 23:59:59 +0000 |
Entrust OV TLS Issuing RSA CA 2 |
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 | Fri, 10 Dec 2027 23:59:59 +0000 |
Subdomains (0)
None observed.
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.
Verify this receiptEd25519 Receipt
- Receipt ID
rcpt_cb5f702a45a4c439- Output Hash
3b00c1fb88db993f2a19071442f02382a21a4d954c17224ca0bbe09e0182af94- Signature
ed25519:01407e18a6c565ecd07b6921fde88c0394c0eb50a9e084267f0ea8a774ff649665d3da6678ebb0490aa612a9d04f64dc87286c1d9ec19d29078a0992b33aac0a- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast