Dataweaz

ril.com

Summary

Registrar
Terranet (India) Private Limited
Status
clientTransferProhibited
Created on
January 4, 1996
Expires on
January 3, 2030
Name servers
ns1.reliance.in, dns.ril.com, ns6.reliance.in, ns5.reliance.in, ns2.reliance.in
Mail servers
GWJGSMTP30.ril.com, gwjgsmtp90.ril.com, gwsmtp20.ril.com, gwsmtp050.ril.com, gwjgsmtp10.ril.com, gwsmtp040.ril.com, gwsmtp80.ril.com, gwhydsmtp20.ril.com, gwjgsmtp020.ril.com, gwsmtp30.ril.com, GWJGSMTP60.ril.com, gwsmtp70.ril.com, gwhydsmtp10.ril.com
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Failure reports
[email protected]

Record

v=DMARC1; p=reject; rua=mailto:[email protected], mailto:[email protected]; ruf=mailto:[email protected]; fo=1

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for ril.com.

RuleValueResult
include_spf1.ril.comAllowed
include_spf2.ril.comAllowed
include_spf.google.comAllowed
includespf.protection.outlook.comAllowed
includesendclean.netAllowed
includencapp02.comAllowed
all—Rejected

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 include:_spf1.ril.com include:_spf2.ril.com include:_spf.google.com include:spf.protection.outlook.com include:sendclean.net include:ncapp02.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
selector1Microsoft 365RSA 1024 bits · shortActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 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 ril.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from ril.com 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 @ril.com 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

ril.com  MX  10 mx1.ril.com.
ril.com  MX  20 mx2.ril.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.ril.com.
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

ril.com  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.ril.com, 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.ril.com  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.ril.com, 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.ril.com  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 ril.com

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.

TypeIP address
A116.50.82.90

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
ns1.reliance.in116.50.96.2
dns.ril.com116.50.96.40
ns6.reliance.in116.50.93.3
ns5.reliance.in116.50.93.2
ns2.reliance.in116.50.96.40

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @ril.com 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
1GWJGSMTP30.ril.com116.50.93.142
1gwjgsmtp90.ril.com116.50.64.114
1gwsmtp20.ril.com116.50.80.189
1gwsmtp050.ril.com116.50.85.104
1gwjgsmtp10.ril.com116.50.64.117
1gwsmtp040.ril.com116.50.80.191
1gwsmtp80.ril.com116.50.96.170
1gwhydsmtp20.ril.com116.50.90.57
1gwjgsmtp020.ril.com116.50.64.116
1gwsmtp30.ril.com116.50.80.188
1GWJGSMTP60.ril.com116.50.90.48
1gwsmtp70.ril.com116.50.80.143
1gwhydsmtp10.ril.com116.50.90.58

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.ril.com.

NameContent
ril.comautodesk-domain-verification=JzGo_nJpuzokDpzayuIh
ril.come18k92rjbhngpj5k55umbcmo22
ril.coms7tmpjrq55mbv4bq7eofmat6ah
ril.comf7c3tgie92s9t1cg6atjo2rcoi
ril.comcursor-domain-verification-s9dayy=R191Q39tsF1Q6xEbWUWjgbB8d
ril.comdbqrt82u1vusgpm2ebugd9jgvt
ril.commdlk5ajeqkonkvtl5dkdbaal1k
ril.comanthropic-domain-verification-1azb3z=n2IyPAztccmlFlTmuZTxxQ3PI
ril.comDrD7pwOdH5rrCuJ7gvFasERke26atdk28ws5GRYooD0=
ril.com2vf6o0jkbtltnmg24i7oi84g8g
ril.com2twuQSaewSddBwHJoausp5v7+Aj28qOeAH1BAIOF/h61tM3vbybYI8eRgUuDIDQclbeDw3tWVTUw8O5/IZNfwg==
ril.comsafebreach-domain-verification=f1445538-15b0-4472-99d2-929c72e89361
ril.comteamviewer-sso-verification=59aa9fd0844f4f7aa2a623b7adae290e
ril.com9jk1g763r1cli5fke4rd1p81sk
ril.comvpce-099aa59883334a82d
ril.comvc45sgqsrp2hhcdokhfe77b52a
ril.comiim3v1j8ae12n8fk1pkrip4obv
ril.comqj3q5ujnjo16nt87ahroqlrgq3
ril.comERG4xZmCRmD9hVvOvjt/bgPKxPw8mcQwREw2AerNCkR3vxqCjn3LLI1qmXXLG4sUeCPGvgitMhgxKyW+naZKpw==
ril.comc4ttpbi15rcr6rbglaqpv47edp
ril.comgoogle-site-verification=jM2P-XDVRsIJ6b-NBs3KMVGqD5TxN6NWvIwwZGMdLPs
ril.coml31s9mknfhrbthv3b5q7kd4n2e
ril.comadobe-idp-site-verification=94be2837c32b44c0a690d235bda4accab2d3bed0cbfe7cfd970a351df71b8f04
ril.comduo_sso_verification=ALHV6hGCTdkweO5kbBTTJIUyIZSFWCgSYXBRPmo4w1wBRYx2HXg1vvBJYtSIiC66
ril.comjg268jk80iludf76tpaaa6lg8k
ril.comgoogle-site-verification=PLVqP8LJDxaLKI3i5iqYlOw-ZqpMAKyv0NrIk2gGUhY
ril.coml7najukgf248r9jritfc5dk68f
ril.comcisco-ci-domain-verification=693593af05efc05a6ec8e7a79412b2e975c90915dffca81da437eed530606bee
ril.comelevenlabs=4RsJL5VROtLv0jWp83pBxCLfRVebFOnEgJFnHYnSg6w
ril.com6rtna6lpf5ii33uhnr3sjqcl9r
ril.comMS=ms75675356
ril.comsafebreach-domain-verification=080d8ab2-2d16-4d23-a868-d1146f3e8d90
ril.com_globalsign-domain-verification=dd2BOQv1ivmN7XCrU_hNflUvgPCfY7TwZu80uTP7zh
ril.comadobe-idp-site-verification=44a67964a5415a8cf240797ba5d616272ba6a84b68f70b6c84e89a5b4ba27b1a
ril.comcursor-domain-verification-7tgfmq=jbrsOmPS2vEET3vWQ2WSWsrUC
ril.com25dobvv5vji0bspbh3650m8gbn
ril.comsafebreach-domain-verification=e6a49665-38f0-433a-8700-efe166ddb128
ril.comhqid3jnju1rv023tcl2j3idrsj
ril.comvoqhdfsun8mpfeu7hdbfa1pjcv
ril.comgoogle-site-verification=vxIqsrZyFqyiuNGfon7SelqGasqTyQQLPMS1zUmKUWs
ril.comvpce-0efb6d170b42d3714
ril.comsg9810rkua3l2j07rsq5et5fb9
ril.comvvgsf7tpnr3vv2ajd120iqhjv
ril.comopenai-domain-verification=dv-j4ej390E2ioCN0PHL29Olcwo
ril.comv=spf1 include:_spf1.ril.com include:_spf2.ril.com include:_spf.google.com include:spf.protection.outlook.com include:sendclean.net include:ncapp02.com -all
_dmarc.ril.comv=DMARC1; p=reject; rua=mailto:[email protected], mailto:[email protected]; ruf=mailto:[email protected]; fo=1
google._domainkey.ril.comv=DKIM1; k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApbe9mZJy27X0r1Hh2p88FZMd7B0KkESxGx5HfWSmuHmxSGMXprFYQxjmHoI8zmBDaTDPRuukTkYV99pVYohdXErslV4dB54P1gEKpmOmWxkwL9h0mexuQCi1FXx8goJ605CThrLSS6sy5Kr34mOpXxD0Aj4QzgWi7P6hq9JsvmPj/zbzyzPJLtipHt+6o5gIUUiZKlDWrrw+IIF3bDYZgs8oQY5kBdSm5/NrIDr/lMEfu7aCvpQfJF+xn0t3CDoCetrjeM3ncO8IcXNIuujkqRCKAksqBdz5rbopCtrEZNNbtEvoX2nzGPyC2P8Zoj9Jln9HgRkSDgy0lw0cryTERQIDAQAB
selector1._domainkey.ril.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCy57AZINropTgnl+Xn9yMdEGFzN8T8xPORpxZukC05Bk4ZtbNyVTd4a0kZcyujpK20lEQ7l+UyFmevR+6yinhGVTJ9ZgPTahQQ843KPjR2oSaPKHoOBivBWY1v1X6PO7BH2QM2YMo0ahIXx1wwxmHgntqh7DlafL5/VDNNXxS0yQIDAQAB;
k2._domainkey.ril.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.ril.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.ril.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApTKGDdNKQ+DdBzH6I8PrlF3TPGwgwckjvGSwGRXihSLqPRKiZiqlNzYKbniRdCPUJ2+gCC/BzznDMALEhfpnCFXiaPCouD1NgdTOyc3FFp2gkqM7/3/3DKksHt5H795ob7b3c9t1ztuZJGyPTlEnvGE3HdeQAn7UBykpyUVc5rRhAkBvFbKqHzBE8e7K/TIeITOeW6DvMG/BhJuY4Zlt78mEku9Oq7Zg4Rhg0VfuP+37MaCGgodNm8Vbw9YR/EsnHHm0JRGiSS3NryarMytSp2kHAb3wRlvtz7l6RDiBNXfR+avIMoY0FpY7ga6F//5JuslHoi2LHI3eXCJmS/ynMwIDAQAB
s2._domainkey.ril.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCsesW4jQddgTJh+0mNTvyJftmNJ3eswn2swddjXxaFQA394j7THXnMxz/N+ClBqOwjn3o8e7mYad8Hj9y+HKoV5mtVZlTQCVS1We67ezPyl4+3ZaROtHahEQUkg6D5optwGm4F/k6G5Y6wTUIik/nfq2S1g0v8a1jPjbPhq75H7wIDAQAB

Related IP addresses

IPv4 addresses used by ril.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
116.50.82.90Website116.50.82.0/24
116.50.96.2Name server ns1.reliance.in116.50.96.0/24
116.50.96.40Name server dns.ril.com, Name server ns2.reliance.in116.50.96.0/24
116.50.93.3Name server ns6.reliance.in116.50.93.0/24
116.50.93.2Name server ns5.reliance.in116.50.93.0/24
116.50.93.142Mail server GWJGSMTP30.ril.com116.50.93.0/24
116.50.64.114Mail server gwjgsmtp90.ril.com116.50.64.0/24
116.50.80.189Mail server gwsmtp20.ril.com116.50.80.0/24
116.50.85.104Mail server gwsmtp050.ril.com116.50.85.0/24
116.50.64.117Mail server gwjgsmtp10.ril.com116.50.64.0/24
116.50.80.191Mail server gwsmtp040.ril.com116.50.80.0/24
116.50.96.170Mail server gwsmtp80.ril.com116.50.96.0/24
116.50.90.57Mail server gwhydsmtp20.ril.com116.50.90.0/24
116.50.64.116Mail server gwjgsmtp020.ril.com116.50.64.0/24
116.50.80.188Mail server gwsmtp30.ril.com116.50.80.0/24
116.50.90.48Mail server GWJGSMTP60.ril.com116.50.90.0/24
116.50.80.143Mail server gwsmtp70.ril.com116.50.80.0/24
116.50.90.58Mail server gwhydsmtp10.ril.com116.50.90.0/24

WHOIS of the domain ril.com

Domain Name: RIL.COM
   Registry Domain ID: 316657_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.dfordomains.com
   Registrar URL: https://dfordomains.com
   Updated Date: 2024-05-15T11:16:16Z
   Creation Date: 1996-01-04T05:00:00Z
   Registry Expiry Date: 2030-01-03T05:00:00Z
   Registrar: Terranet (India) Private Limited
   Registrar IANA ID: 1337
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +91.2240611166
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: DNS.RIL.COM
   Name Server: NS1.RELIANCE.IN
   Name Server: NS2.RELIANCE.IN
   Name Server: NS5.RELIANCE.IN
   Name Server: NS6.RELIANCE.IN
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T14:38:58Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.