Dataweaz

ora.ai

Summary

Registrar
GoDaddy.com, LLC
Status
clientDeleteProhibited
Created on
December 16, 2017
Expires on
March 6, 2029
Name servers
ns2.vercel-dns.com, ns1.vercel-dns.com
Mail servers
smtp.google.com
SPF
Soft

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

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

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
—
Failure reports
—

Record

v=DMARC1; p=none;

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 ora.ai.

RuleValueResult
include_spf.google.comAllowed
include148649656.spf04.hubspotemail.netAllowed
all—Suspicious

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:_spf.google.com include:148649656.spf04.hubspotemail.net ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive

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 ora.ai arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from ora.ai 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 @ora.ai 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

ora.ai  MX  10 mx1.ora.ai.
ora.ai  MX  20 mx2.ora.ai.

What the record contains

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

ora.ai  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.ora.ai, 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.ora.ai  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.ora.ai, 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.ora.ai  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 ora.ai

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
ns2.vercel-dns.com198.51.45.13
ns1.vercel-dns.com198.51.44.13

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @ora.ai 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.com74.125.133.26

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.ora.ai.

NameContent
ora.aiapple-domain-verification=JLy7kICs2O2kwQCb
ora.aigoogle-gws-recovery-domain-verification=71402152
ora.aiv=spf1 include:_spf.google.com include:148649656.spf04.hubspotemail.net ~all
ora.aismithery-verification=9938d6ff0faa91da16bac072c0d1a9b9b7cb2769062f067c81d1f732ea00db28
ora.aigoogle-site-verification=xAUdHQBib6GvwnbFwwCZzLKfXnroVoNR2PIzD_lRhtQ
ora.aiins_3CGGekYmTCLc7qR8ALi8SnDdErr
ora.aigoogle-site-verification=Z9IPk9oQGho0TgjKIz8oDvDTtmZjPTc23DdOpVE5Czo
_dmarc.ora.aiv=DMARC1; p=none;
google._domainkey.ora.aiv=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuGNG/IjtXF4HF5zsDXZzFgnIfFBR5ZzDrw4x54Sz1lL0YPPjGDYDnJOwB/vyV48OVicW4zpE4QEKu7tj20Ou8TtArnlxBZQ47chdid5u4h+KcjcJeZ8PdM28FnGnERTQes//Lwltznl/1eqesiRbCkTADqZ7jYzJGS8jt4sZtsoWr1L+6tdUcPNLF7SCyfLe7cbhniIAlccozv1wLvp/az2uHxCbSjGqe7wXXCmuCA+qHc8ZueYJm4AQoDaC0OAGFS2TCPtxaTBQfumOH+czDUiYviNodbO0WJvSP6g8QsiCUiRuTPpOmRdmJ3UdRuafpNgj00B1hB9KINwDl2CcCQIDAQAB
s1._domainkey.ora.aik=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4gid1BAh2H1CYxQcolKqEKUMa6rqWJQ+9DUjJ1DQmyBQ1tpwBG9CEyYoH0JLH7arJCwZDk0LkLi44xuYbYuObfVcuw3T1JhAo9ZHpKCX5Zfc7m0ofiu2Oq6DtEJL732Oop98Er209RSdk8LiR/ifBZ83DXrRYTtH/gyPnSiOsS/ywjK8KJlodZgDYsFoK+7xCAJyiV/okUodxaFIvkEXCMvq/XDgOZVKTItL97q1okyFMCKQUMKDoy0ch0bYZKzK92/EwO2jcVuHxHLZ9DJbRaiQzah9kD9FkRxkc9X863ZUiaTgmE808jhD+kB/PwjD+tWyhnq+7pEVYEcVhOjACwIDAQAB
s2._domainkey.ora.aik=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtAAzrUKF8TFMR5f9g65OyglWMzGuHx0MYvvSF4f4KgbqS4A5sRsj5oaE10NlkDFOAAVyeENQzGCNF/LfIcuPNFSIFkqjoUvl8AaWzwRwxqzaaAm2U9cRTl23W4bIQdp/n6mp4V/tfihxvrL3FAjIFsY+Xd6JPGd8JzDldMTvJwzNhH7ZbewP+dHWsmbBvlgH+gwclxtVLIPXGJ+yqldNmSTGTv85gLl2mVmgNwR5v9ZvDuCfWUS82us6xgctfQ4Q1/ghrVr3HfBBKf6MMTS2ZJgslAse9c2+Lql+dsLuADU7sLsa2CByro4AuD4fJOCjmPg1AKy3LmX4U+QoMTQ4bwIDAQAB

Related IP addresses

IPv4 addresses used by ora.ai: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
216.150.1.129Website216.150.1.0/24
216.150.16.1Website216.150.16.0/24
198.51.45.13Name server ns2.vercel-dns.com198.51.45.0/24
198.51.44.13Name server ns1.vercel-dns.com198.51.44.0/24
74.125.133.26Mail server smtp.google.com74.125.133.0/24

WHOIS of the domain ora.ai

Domain Name: ora.ai
Registry Domain ID: e9fe618b23304103896b37e3aab0127e-DONUTS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com/domains/search.aspx?ci=8990
Updated Date: 2026-08-12T06:08:02Z
Creation Date: 2017-12-16T04:01:06Z
Registry Expiry Date: 2029-03-06T04:01:06Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: 45b74c72f2c0470da23235837d9f9d3b-DONUTS
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com 100 S. Mill Ave, Suite 1600
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85281
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: [email protected]
Registry Admin ID: 45bee38ac86d4f578ab9a014b900a8e9-DONUTS
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com 100 S. Mill Ave, Suite 1600
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85281
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: [email protected]
Registry Tech ID: 9631ab2a3bd442949d41b37d3ec345f0-DONUTS
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com 100 S. Mill Ave, Suite 1600
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85281
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: [email protected]
Name Server: ns1.vercel-dns.com
Name Server: ns2.vercel-dns.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T10:00:38Z <<<

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

Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Domain Name: ora.ai
Registry Domain ID: e9fe618b23304103896b37e3aab0127e-DONUTS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2026-05-20T20:35:06Z
Creation Date: 2017-12-16T04:01:06Z
Registrar Registration Expiration Date: 2029-03-06T04:01:06Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: cr924633656
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 100 S. Mill Ave, Suite 1600
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85281
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: 
Registrant Fax Ext:
Registrant Email: https://www.godaddy.com/whois/results.aspx?domain=ora.ai&action=contactDomainOwner
Registry Tech ID: cr924633657
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 100 S. Mill Ave, Suite 1600
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85281
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: 
Tech Fax Ext:
Tech Email: https://www.godaddy.com/whois/results.aspx?domain=ora.ai&action=contactDomainOwner
Name Server: NS1.VERCEL-DNS.COM
Name Server: NS2.VERCEL-DNS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T10:00:38Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

**NOTICE** This WHOIS server is being retired. Please use our RDAP service instead.

% Query time: 865 msec
% WHEN: Thu Oct 01 10:00:37 UTC 2026