Audit of 284 Russian Websites Finds Email, DNS and Data Protection Issues
An audit of 284 websites run by major Russian organizations found issues with DMARC, DNS, outdated libraries and third-party services. Automated findings still need manual verification.
On November 9, 2026, an author on Habr described an audit of 284 websites run by major Russian organizations, from banks and retailers to universities and government agencies. His tool looked for problems with email, DNS, server settings and dependencies, as well as discrepancies with personal data processing policies. Of the 275 domains for which DMARC data was available, 66 had no record or had one set to p=none — 24%. Website owners have good reason to check their settings: an automated finding does not, by itself, prove that a site has been hacked or is breaking the law.
Email and subdomains: what was left unattended
Of the 275 domains, 22 had no DMARC record, while another 44 had a p=none policy. That setting allows reports to be collected but does not require messages that fail authentication to be blocked. A p=quarantine policy was in place for 108 domains, and p=reject for 101. These records set rules for receiving mail servers, but the author did not check whether any particular message was delivered.
Even protection on the primary domain did not always extend to subdomains. The author found 42 cases with sp=none: mail from the primary domain could be subject to a strict policy while mail from a subdomain was not. That is why checking only the p= value is not enough.
Another risk involves discontinued projects. Five subdomains pointed to cloud resources that no longer existed: four in AWS and DigitalOcean, and one in cloud storage. If someone can claim a resource again, a page controlled by someone else could potentially appear at the company’s address. The author did not attempt to claim any resources and labels these cases as possible takeovers requiring manual confirmation.
Outdated code and third-party integrations
The tool could read pages on 170 websites; the others restricted crawler access. On 24% of the accessible sites, it detected old versions of JavaScript libraries with known vulnerabilities, including jQuery 1.10, 1.11, 1.12 and 2.2. The presence of one of these versions does not mean a vulnerability is exploitable: it depends on how the site uses the library. But it is a reason to review dependencies rather than leave them untouched until the next redesign.
HSTS was absent from 57% of sites, and 31% of servers accepted TLS 1.0 or 1.1. At the time of the audit, certificates on 12 sites were due to expire within two weeks. The author found a properly configured Content Security Policy (CSP) on only two of 184 sites. Each result needs to be checked on the relevant server; taken together, they show how many settings fall outside routine work on web pages.
Foreign services appeared among the third-party integrations on 51% of sites, most often Google Analytics. In 31% of cases, the privacy policy’s description of data processing did not match the services loaded by the page. According to the author’s observations, IP addresses, and sometimes cookies, are passed to third-party services as soon as the site opens. The article discusses this in the context of Russia’s Federal Law No. 152-FZ and the requirement to notify Roskomnadzor in advance of cross-border data transfers. But the presence of a script is no substitute for a legal assessment of what a particular company does.
What website owners should check
A starting point is the company’s email domains: compare every service that sends mail on its behalf with its SPF and DMARC settings, then review the reports. The author suggests moving from p=none to p=quarantine and then to p=reject, while checking subdomains separately. Switching straight to reject without accounting for the company’s own mailings could stop some messages from getting through.
Next, compare DNS records with active projects and remove records pointing to discontinued cloud resources. Developers should check library versions, TLS, HSTS and CSP. Marketers and those responsible for personal data should review the installed tracking tools and the policy text together. A change to the page is easy to miss when the document is updated separately from the site.
The findings have limits: some pages were closed to the crawler, possible subdomain takeovers were not confirmed by claiming resources, and the tool’s accuracy on live sites has not yet been measured against manually labeled results. The author had to correct his initial summary because he used the wrong denominator to calculate the share of one phishing scenario. Before making changes, it is therefore worth comparing the evidence in the report — DNS records, response headers and script URLs — with the site’s current state.
My take: a report is for action, not alarm
I would not turn these percentages into a ranking of unsafe companies. The sample is mixed, some pages are inaccessible to the scanner, and an old library is not the same as a working attack. It is more useful to create verifiable tasks and assign owners for email, DNS, server settings, dependencies and third-party scripts.
What concerns me more is the disconnect between teams. If a marketer adds a tracking tool, a lawyer updates the policy, and a developer changes the page, but no one checks the result against the others, the document stops describing the website. A scanner can flag the mismatch; people still have to decide what to fix.
Sources
Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.
Full-stack developer
I optimize web applications and handle the back end for small services. In discussions, I try to distinguish “fast for the demo” from “reliable a year from now.”
All posts by the authorRelated articles
Critical Vulnerabilities in Open-Source Software Rise Nearly Fivefold
From January to September 2026, CodeScoring recorded nearly five times as many critical open-source vulnerabilities as a year earlier. Site owners and teams should check the versions of the components they use.
PHP Core Vulnerabilities Patched That Could Allow Remote Code Execution
PHP has patched core vulnerabilities that could lead to remote code execution and process memory disclosure. Website owners should check their PHP version and install the security update.
Breach of .gh, .sl and .as Registry Infrastructure Enabled Unauthorized TLS Certificates
Attackers compromised the infrastructure behind the .gh, .sl and .as domains, changed DNS records and obtained unauthorized HTTPS certificates, including for Google domains. Google blocked them in Chrome and advises site owners to check CT logs.
Discussion 4
Pavel Novák
One useful follow-up is to turn findings like outdated libraries and third-party integrations into an ownership map: assign each dependency a maintainer and a review date, or it’ll quietly drift again after the audit.
Tural Latyp
Did the audit manually verify the 66 DMARC findings, or were they all based on DNS records alone?
Tomas Vaitkus Post author
As described, the 66 are DNS-record findings: 22 domains had no DMARC record and 44 had `p=none`. The report doesn’t say those were manually verified, so I’d treat them as configuration observations, not evidence of spoofing or a compromise.
Piotr Zieliński
@tural_l, in store audits I’ve seen a DNS scan flag DMARC as “missing” when the record was actually published on the correct organizational domain, not the specific subdomain being checked. So I’d treat the 66 as a useful triage list, but verify the record at the right DNS name and check the policy in context before calling it a protection gap.