Dataweaz

oko.press

Summary

Registrar
Cloudflare, Inc.
Status
clientTransferProhibited
Created on
March 31, 2016
Expires on
April 1, 2027
Name servers
ns4.oko.press, ns3.oko.press, ns5.oko.press, ns1.oko.press, ns2.oko.press
Mail servers
smtp.google.com, aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
SPF
Soft

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

DMARC tells mail servers what to do with an e-mail that claims to come from oko.press but fails SPF and DKIM checks.

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
5%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=quarantine; pct=5; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for oko.press.

RuleValueResult
include_spf.google.comAllowed
includeservers.mcsv.netAllowed
all—Suspicious

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:_spf.google.com include:servers.mcsv.net ~all

E-mail signing (DKIM)

DKIM keys published by oko.press under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
k1MailchimpRSA 1024 bits · shortActive
mandrillMandrillRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to oko.press arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from oko.press was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @oko.press address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

oko.press  MX  10 mx1.oko.press.
oko.press  MX  20 mx2.oko.press.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.oko.press.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

oko.press  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.oko.press, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.oko.press  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.oko.press, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.oko.press  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of oko.press

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns4.oko.press162.159.11.156
ns3.oko.press162.159.10.86
ns5.oko.press173.245.58.16
ns1.oko.press162.159.8.123
ns2.oko.press162.159.9.169

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @oko.press addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
1smtp.google.com142.251.173.26
10aspmx.l.google.com142.251.168.26
20alt2.aspmx.l.google.com142.251.127.26
20alt1.aspmx.l.google.com192.178.213.27
30alt3.aspmx.l.google.com172.253.148.26
30alt4.aspmx.l.google.com142.250.147.27

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.oko.press.

NameContent
oko.pressatlassian-domain-verification=GpPKgALIdKtpHmWRTT292UMtwCMV9IgXP78bzDKdKNke6fyxSyNC8lpFfFOo9LIL
oko.presscanva-site-verification=GciRUzZIRpm_iea9rm3zJw
oko.pressgoogle-site-verification=EBdOQ9in96h8jYiIUnqUFM55YJlU3jntCC_ufwz2oMM
oko.pressv=spf1 include:_spf.google.com include:servers.mcsv.net ~all
oko.press2c65702d15c3e54efa4f56d8711e31909abfe47c6a4790cf800de5845e699a7
oko.press6f5ac4c786a75e2aea672ab8edd458e6c5b20f5ec5ea93f02f69541c38988ee
oko.pressMS=568D7E48AB3657C702F2586BEC1C4A8152BE790D
oko.pressMS=ms16083638
oko.pressa119bba89311712bfe4435e377e5754c2a4e6230f29b412c4c65860d57432f6
_dmarc.oko.pressv=DMARC1; p=quarantine; pct=5; rua=mailto:[email protected]
google._domainkey.oko.pressv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnuYF6SJLCtyAI8aSNjwRdEfvdJaLvNJnDESBmcD8f+M1gWYChsQtz34RMlHaH2E3hJJEmUbSpEeyNuSdobHk/H34DWCo6g+0pz6t8llIIFY985x80bfpTEsGsAeOFPsLrXV9oCijilui9CfvDgp2qdD6bxC95ZRTySAsljRyXOWH3M51FSiMalM3PAHsjCfj92Rt6gAxq1wSl9Hfh0d90uf1LeASlohm7rrkDW6lvSmuviHSqhDGE4OQ+U6GwdCuy/grxAKeAdkAZkm9PVbiyKUjz4mNV7gqpNix6lmrljUToo4FVUQHgpZ/yMb+HqmO4tK72S6yGN1r+dgB5INBWQIDAQAB
k1._domainkey.oko.pressk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
mandrill._domainkey.oko.pressv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;

Related IP addresses

IPv4 addresses used by oko.press: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
104.20.41.194Website104.20.41.0/24
172.66.160.252Website172.66.160.0/24
162.159.11.156Name server ns4.oko.press162.159.11.0/24
162.159.10.86Name server ns3.oko.press162.159.10.0/24
173.245.58.16Name server ns5.oko.press173.245.58.0/24
162.159.8.123Name server ns1.oko.press162.159.8.0/24
162.159.9.169Name server ns2.oko.press162.159.9.0/24
142.251.173.26Mail server smtp.google.com142.251.173.0/24
142.251.168.26Mail server aspmx.l.google.com142.251.168.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.26Mail server alt3.aspmx.l.google.com172.253.148.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24

WHOIS of the domain oko.press

Domain Name: oko.press
Registry Domain ID: D19289454-CNIC
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://domains.cloudflare.com
Updated Date: 2026-03-06T04:07:18.000Z
Creation Date: 2016-03-31T07:10:42.000Z
Registry Expiry Date: 2027-03-31T23:59:59.000Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.8889935273
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: jason.ns.cloudflare.com
Name Server: lana.ns.cloudflare.com
DNSSEC: signedDelegation
URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

>>> Last update of WHOIS database: 2026-10-02T12:55:31.427Z <<<

For more information on domain status codes, please visit https://icann.org/epp

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Tucows Registry for informational
purposes only, and it does not guarantee its accuracy. Tucows Registry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Tucows Registry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass  unsolicited, commercial advertising
or solicitations to entities other than your existing  customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Tucows Registry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.
Domain Name: OKO.PRESS
Registry Domain ID: D19289454-CNIC
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2026-03-16T08:52:11Z
Creation Date: 2016-03-31T07:10:42Z
Registrar Registration Expiration Date: 2027-03-31T23:59:59Z
Registrar: Cloudflare, Inc.
Registrar IANA ID: 1910
Domain Status: clienttransferprohibited https://icann.org/epp#clienttransferprohibited
Registry Registrant ID:
Registrant Name: DATA REDACTED
Registrant Organization: DATA REDACTED
Registrant Street: DATA REDACTED
Registrant City: DATA REDACTED
Registrant State/Province: MAZOWIECKIE
Registrant Postal Code: DATA REDACTED
Registrant Country: PL
Registrant Phone: +1.4153197517
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: 
Name Server: jason.ns.cloudflare.com
Name Server: lana.ns.cloudflare.com
DNSSEC: signedDelegation
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4153197517
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-02T12:55:31Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Cloudflare provides more than 13 million domains with the tools to give their global users a faster, more secure, and more reliable internet experience.

NOTICE:

Data in the Cloudflare Registrar WHOIS database is provided to you by Cloudflare
under the terms and conditions at https://www.cloudflare.com/domain-registration-agreement/

By submitting this query, you agree to abide by these terms.

Register your domain name at https://www.cloudflare.com/registrar/

% Query time: 867 msec
% WHEN: Fri Oct 02 12:55:30 UTC 2026