Digital exposure report
iate.obninsk.ru
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-18 01:56 UTC
Partial coverage: the score is based on 40% of applicable check weight. 10 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.iate.obninsk.ru
- 2.
Send visitors to the secure version of your site
Visitors who type your address without https may stay on an unprotected connection.
Who can fix it: Your web host
How to verify after the fix
curl -sI http://iate.obninsk.ru/ | grep -iE "^(HTTP|location)"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- iate.obninsk.ru
- Website request
- GET https://iate.obninsk.ru/
- Scan time
- 2026-11-18 01:56:05 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
- HTTPS available · Unverified
- SSL/TLS certificate validity · Unverified
- HSTS — enforce encryption in the browser · Unverified
- CSP — protection from script injection · Unverified
- Clickjacking protection · Unverified
- X-Content-Type-Options · Unverified
- Referrer-Policy · Unverified
- Permissions-Policy · Unverified
- DNSSEC — signed DNS records · Unverified
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 9/25 | An attacker can send email that looks like it came from the company. |
| Encryption & certificate | 0/7 | Browsing to the site is not properly protected by encryption. |
| Browser protections | — | Nothing in this category could be verified from public data. |
| DNS infrastructure | 3/8 | The domain's infrastructure lacks basic protections. |
Fix priorities
- 1.HighHTTP → HTTPS redirect · Hardening gap+18
- 2.HighDMARC — anti-spoofing policy · Hardening gap+38
- 3.LowCAA — who may issue certificates · Hardening gap+13
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- HTTPS available
- SSL/TLS certificate validity
- CSP — protection from script injection
- HSTS — enforce encryption in the browser
- DNSSEC — signed DNS records
- Clickjacking protection
- DKIM — digital signature on email
- X-Content-Type-Options
- Referrer-Policy
- Permissions-Policy
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 2 of 10 DNS lookups.
v=spf1 a mx ip4:195.112.97.194 ~all
$ dig +short TXT iate.obninsk.ru
DMARC — anti-spoofing policy
Failed · Severity: High · Hardening gap · 0/15No policy tells mail servers to block forged email in the company's name — a common opening for CEO fraud and phishing.
No TXT record at _dmarc.iate.obninsk.ru. Without DMARC, mail failing SPF/DKIM may still reach the inbox.
(no DMARC record found)
$ dig +short TXT _dmarc.iate.obninsk.ru
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.iate.obninsk.ru. TXT "v=DMARC1; p=none; rua=mailto:dmarc@iate.obninsk.ru; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.iate.obninsk.ru
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
3 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mail.iate.obninsk.ru 50 email.iate.obninsk.ru 90 basic.maxnet.ru
$ dig +short MX iate.obninsk.ru
HTTPS available
Unverified · Severity: OK · Not scoredHTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.
Requesting https://iate.obninsk.ru/ didn't complete (HTTP 521). Timeouts and transport errors may be transient; the check is excluded from the score.
HTTP 521
$ curl -svI https://iate.obninsk.ru/ 2>&1 | grep -E "SSL|HTTP|expire"
HTTP → HTTPS redirect
Failed · Severity: High · Hardening gap · 0/7The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.
http://iate.obninsk.ru/ returned HTTP 200 without redirecting to https://.
HTTP 200 Location: (none)
$ curl -sI http://iate.obninsk.ru/ | grep -iE "^(HTTP|location)"
- Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
- Then add an HSTS header.
server {
listen 80;
server_name iate.obninsk.ru www.iate.obninsk.ru;
return 301 https://$host$request_uri;
}Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.
SSL/TLS certificate validity
Unverified · Severity: OK · Not scoredThe certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.
No live TLS evidence was obtained. CT entries are shown as context only. Not scored.
CT logs (context only, not scored): Issuer: GlobalSign Valid from: 2025-12-29 Valid until: 2027-01-30 Names: *.iate.obninsk.ru, iate.obninsk.ru Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect iate.obninsk.ru:443 -servername iate.obninsk.ru 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
CSP — protection from script injection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
Clickjacking protection
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
X-Content-Type-Options
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
Referrer-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
Permissions-Policy
Unverified · Severity: OK · Not scoredCouldn't be checked — no usable HTTPS response was obtained. Not scored.
No response with headers was received, so this header wasn't evaluated and is excluded from the score.
No HTTPS response received
$ curl -sIL https://iate.obninsk.ru/
DNSSEC — signed DNS records
Unverified · Severity: OK · Not scoredDNSSEC status couldn't be determined from passive queries. Not scored.
No AD flag was returned, but a missing AD flag alone doesn't prove the zone is unsigned. Check DS at the parent and validate with delv or DNSViz.
Cannot be determined AD = false DS iate.obninsk.ru: nxdomain
$ dig +short DS iate.obninsk.ru delv iate.obninsk.ru
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA iate.obninsk.ru
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
iate.obninsk.ru. CAA 0 issue "letsencrypt.org" iate.obninsk.ru. CAA 0 iodef "mailto:security@iate.obninsk.ru"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
ns.iate.obninsk.ru ns.maxnet.ru
$ dig +short NS iate.obninsk.ru
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 observed gaps · 1 unverified
- PCI DSS v4.01 observed gaps · 5 unverified
- NIS2 / vendor due diligence2 observed gaps · 4 unverified
- SOC 2 / ISO 27001 baseline1 observed gaps · 6 unverified
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | iate.obninsk.ru | 195.112.97.194 |
| AAAA | iate.obninsk.ru | — |
| MX | iate.obninsk.ru | 10 mail.iate.obninsk.ru | 50 email.iate.obninsk.ru | 90 basic.maxnet.ru |
| NS | iate.obninsk.ru | ns.iate.obninsk.ru | ns.maxnet.ru |
| TXT | iate.obninsk.ru | facebook-domain-verification=p88xczo9rvxxzc7bzv0ou6yxwzly4i | _globalsign-domain-verification=BnFRrYz0dYVtK5Wfr-jeDbQRwieGLZj8Fc3zIIP5-0 | v=spf1 a mx ip4:195.112.97.194 ~all |
| TXT | _dmarc.iate.obninsk.ru | — |
| CAA | iate.obninsk.ru | — |
| DS | iate.obninsk.ru | — |