Summary
- Registrar
- Regional Network Information Center, JSC dba RU-CENTER
- Status
- clientTransferProhibited
- Created on
- December 4, 2010
- Expires on
- December 4, 2026
- Name servers
- ns1.ren-tv.com, ns2.ren-tv.com, ns3.ren-tv.com, ns6.ren-tv.com, ns4.ren-tv.com, ns5.ren-tv.com
- Mail servers
- mx.ren-tv.com
- DMARC
- Reject
- SPF
- Delegated
- DKIM
- 1 key found
- Website
- See the website
Spoofing protection (DMARC)
E-mails spoofing this domain are rejected.
DMARC tells mail servers what to do with an e-mail that claims to come from ren.tv but fails SPF and DKIM checks.
- Policy
- Reject
- Subdomain policy
- Reject
- Messages covered
- 100%
- DKIM alignment
- Strict
- SPF alignment
- Strict
- Aggregate reports
- [email protected]
- Failure reports
- [email protected]
Record
v=DMARC1;p=reject;sp=reject;pct=100;adkim=s;aspf=s;fo=1;rua=mailto:[email protected];ruf=mailto:[email protected]
Authorized senders (SPF)
The policy is defined by the domain ren-tv.com (redirect).
SPF lists the servers allowed to send e-mails for ren.tv.
| Rule | Value | Result |
|---|---|---|
| redirect | ren-tv.com | — |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 redirect=ren-tv.com
E-mail signing (DKIM)
DKIM keys published by ren.tv under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| — | RSA 2048 bits | Active |
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 ren.tv arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from ren.tv 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 @ren.tv 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
ren.tv MX 10 mx1.ren.tv. ren.tv MX 20 mx2.ren.tv.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.ren.tv.
- 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
ren.tv 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.ren.tv, 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.ren.tv 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.ren.tv, 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.ren.tv 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 ren.tv
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.
| Type | IP address |
|---|---|
| A | 185.178.208.3 |
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.
| Server | IP address |
|---|---|
| ns1.ren-tv.com | 185.231.232.13 |
| ns2.ren-tv.com | 89.20.33.101 |
| ns3.ren-tv.com | 89.20.40.115 |
| ns6.ren-tv.com | 185.70.164.40 |
| ns4.ren-tv.com | 46.46.155.210 |
| ns5.ren-tv.com | 95.213.167.227 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @ren.tv 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.
| Priority | Server | IP address |
|---|---|---|
| 10 | mx.ren-tv.com | 89.20.33.101 |
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.ren.tv.
| Name | Content |
|---|---|
| ren.tv | v=spf1 redirect=ren-tv.com |
| ren.tv | yandex-verification: 2cb73571253179ab |
| ren.tv | google-site-verification=yVonq95IvIPaVjBGU4ujJKHovvkXcF9VKivYQK9P4pU |
| _dmarc.ren.tv | v=DMARC1;p=reject;sp=reject;pct=100;adkim=s;aspf=s;fo=1;rua=mailto:[email protected];ruf=mailto:[email protected] |
| mail._domainkey.ren.tv | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAin1P6tOS83imw3fSjp6M1Uo2Xqz0cJsI1OradOUTwAtzk/2/l6eIud4pASf/uQJv2amt7DGx6ZDnyFJmgM2FX9xX7bz3DkaCZfLfO1E6YhZgffydYWzzOLfavJgJ70D+koR2qoV59HjIwQ+sDdjZov6v4++zF3rZbsV+6dC5IT06T23bHP9Jy9kmRMNebDLxWwtpv8mTooMFmcd+g0mBRFmay3Rg/goIsfZTWQvNnLyVe+Qt/Xya3njNXiQYZFs0jIY0J3lIn256dHNY19uOUSLvWxJEyT7wqmbihfbUMPsiAHOHgZrLScUXfSOMrFqdMuX8Zv5a/yA+015mcCqnXwIDAQAB |
Related IP addresses
IPv4 addresses used by ren.tv: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 185.178.208.3 | Website | 185.178.208.0/24 |
| 185.231.232.13 | Name server ns1.ren-tv.com | 185.231.232.0/24 |
| 89.20.33.101 | Name server ns2.ren-tv.com, Mail server mx.ren-tv.com | 89.20.33.0/24 |
| 89.20.40.115 | Name server ns3.ren-tv.com | 89.20.40.0/24 |
| 185.70.164.40 | Name server ns6.ren-tv.com | 185.70.164.0/24 |
| 46.46.155.210 | Name server ns4.ren-tv.com | 46.46.155.0/24 |
| 95.213.167.227 | Name server ns5.ren-tv.com | 95.213.167.0/24 |
WHOIS of the domain ren.tv
Domain Name: ren.tv Registry Domain ID: REDACTED FOR PRIVACY Registrar WHOIS Server: Registrar URL: www.nic.ru Updated Date: 2025-12-08T01:10:56Z Creation Date: 2010-12-04T09:00:58Z Registry Expiry Date: 2026-12-04T09:00:58Z Registrar: Regional Network Information Center, JSC dba RU-CENTER Registrar IANA ID: 463 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +7.4959944601 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: "REN TV CHANNEL LLC" Registrant Street: REDACTED FOR PRIVACY Registrant Street: REDACTED FOR PRIVACY Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: RU Registrant Phone: REDACTED FOR PRIVACY Registrant Phone Ext: REDACTED FOR PRIVACY Registrant Fax: REDACTED FOR PRIVACY Registrant Fax Ext: REDACTED FOR PRIVACY Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Admin ID: Admin Name: Admin Organization: Admin Street: Admin Street: Admin Street: Admin City: Admin State/Province: Admin Postal Code: Admin Country: Admin Phone: Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Phone Ext: REDACTED FOR PRIVACY Tech Fax: REDACTED FOR PRIVACY Tech Fax Ext: REDACTED FOR PRIVACY Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: ns1.ren-tv.com Name Server: ns2.ren-tv.com Name Server: ns5.ren-tv.com Name Server: ns6.ren-tv.com Name Server: ns4.ren-tv.com Name Server: ns3.ren-tv.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T23:47:19Z <<< For more information on Whois status codes, please visit https://icann.org/epp The Service is provided so that you may look up certain information in relation to domain names that we store in our database. Use of the Service is subject to our policies, in particular you should familiarise yourself with our Acceptable Use Policy and our Privacy Policy. The information provided by this Service is 'as is' and we make no guarantee of it its accuracy. You agree that by your use of the Service you will not use the information provided by us in a way which is: * inconsistent with any applicable laws, * inconsistent with any policy issued by us, * to generate, distribute, or facilitate unsolicited mass email, promotions, advertisings or other solicitations, or * to enable high volume, automated, electronic processes that apply to the Service. You acknowledge that: * a response from the Service that a domain name is 'available', does not guarantee that is able to be registered, * we may restrict, suspend or terminate your access to the Service at any time, and * the copying, compilation, repackaging, dissemination or other use of the information provided by the Service is not permitted, without our express written consent. This information has been prepared and published in order to represent administrative and technical management of the TLD. We may discontinue or amend any part or the whole of these Terms of Service from time to time at our absolute discretion. % Query time: 735 msec % WHEN: Thu Oct 01 23:47:19 UTC 2026