Dataweaz

speechify.com

Summary

Registrar
Cloudflare, Inc.
Status
clientTransferProhibited
Created on
May 8, 2013
Expires on
May 8, 2031
Name servers
christian.ns.cloudflare.com, irena.ns.cloudflare.com
Mail servers
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
DMARC
Reject
SPF
Soft

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 speechify.com but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=reject; pct=100; 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 speechify.com.

RuleValueResult
include_spf.google.comAllowed
includemg-spf.greenhouse.ioAllowed
include_spf.firebasemail.comAllowed
all—Suspicious

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 include:_spf.google.com include:mg-spf.greenhouse.io include:_spf.firebasemail.com ~all

E-mail signing (DKIM)

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

speechify.com  MX  10 mx1.speechify.com.
speechify.com  MX  20 mx2.speechify.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.speechify.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

speechify.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.speechify.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.speechify.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.speechify.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.speechify.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 speechify.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
A172.67.68.119
A104.26.1.186
A104.26.0.186
AAAA2606:4700:20::681a:ba
AAAA2606:4700:20::ac43:4477
AAAA2606:4700:20::681a:1ba

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
christian.ns.cloudflare.com172.64.35.247
irena.ns.cloudflare.com172.64.34.79

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @speechify.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
1aspmx.l.google.com64.233.167.27
5alt1.aspmx.l.google.com192.178.213.26
5alt2.aspmx.l.google.com142.251.127.26
10alt3.aspmx.l.google.com172.253.148.27
10alt4.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.speechify.com.

NameContent
speechify.comgoogle-site-verification=0NMx-vPGfL_G8y8xC5qeUe0wFb9P01EuGVpNbHY4GOw
speechify.comgoogle-site-verification=FL-iUFvzm5PJcPKoNOqVHt1AviYT7L7HTB5bcIihGx4
speechify.comgoogle-site-verification=IxuVU02JK7dOxZfU7nH22nesDtT7pFk_6Fbt1QPqgjM
speechify.comgoogle-site-verification=JLtCZkD8Pksdg8kCg_hej81HW035T_fDecbwPZvvpxk
speechify.comgoogle-site-verification=Yu8kzUcEnqfRXn_8COF1C1d06jfTRVDFi8ctRfkaw0o
speechify.comgoogle-site-verification=_PFFxP_7WQCgP2rc2wGD1bkBXVfMsp3hVM2VddtU3_g
speechify.comgoogle-site-verification=jOgzn6XqgeyR4XKT3Zk1CBBwBBEq7h0tM_TcpDRzldI
speechify.comgoogle-site-verification=kjf24vPJMikiyelPK8LJvuzm68DQL_59Y0FZcEYujz8
speechify.comgoogle-site-verification=tJdLxdoFlpUJHPVfMi2TSr-TYhUtXsgFK1R_imQx1YI
speechify.comgoogle-site-verification=w8xFo-VjVA36G3fJxjGCUBSBwFaHdLcRctCZncVyVd0
speechify.comgoogle-site-verification=xKbt-vedrz2QVy4demgOMtNu0oxDMgTlRaxhPcp2byY
speechify.comgoogle-site-verification=zWHRDDnmY3eOfFnOzdr9uWF5Y2987stx5alSSgT5JNY
speechify.comslack-domain-verification=mFBi1tulc0kQXFybB5MftPT0dgSw4Ew30Mrt24s5
speechify.comtiktok-developers-site-verification=2YQmS5K06QxxCpVgOYk1V5grx28TIC4G
speechify.comtiktok-developers-site-verification=Ea6ys5DBLXbIIAoIYQ6vxWI8FGa028s6
speechify.comtiktok-developers-site-verification=WJe1RhthcRLhQdSHlwcdhK83EFYDWTxE
speechify.comv=spf1 include:_spf.google.com include:mg-spf.greenhouse.io include:_spf.firebasemail.com ~all
speechify.comwork-os-domain-verification-amwvmj=WRbEQukKnawXBczo8fi1zpVm7
speechify.comMS=ms17961709
speechify.combrevo-code:12e857ce7d2475c03d0520cb1abfeea2
speechify.comcloudflare_dashboard_sso=3ee2459d2ef47fe687018d4ace85f3bf
speechify.comfirebase=speechifymobile
_dmarc.speechify.comv=DMARC1; p=reject; pct=100; rua=mailto:[email protected]
google._domainkey.speechify.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAky8xPZ5ni2xezBXn9a3xLZZimFUJPbZTrIZVq9P1bjf0s+s7jtiwYw1wQCJvJ4NPJT+DaxgR5RWkyEG7CEFnw7um1XpPimRsaV18TUZN63uyz5Wjrs2ByS5V9wZphnikoiYeAhfmzbwFiM9/I4Yrn/XnTmPyV0n7QHSPBSxujwGo0nOpNfWdVBRoCgH7kFWN+x2WqyzvG421GG83qC43Aw0OLOsFxr8LmhQpZKq+g3IW0UrRJV07MImvGfxZeFJKdP60RzNN9uMTiPuwmtCeTUu+zf40sR1lUZdIuQOCQSqsI+Wczlz3neUN7MOfDloRPcfNozSQB+apbcufjTgb4QIDAQAB
s1._domainkey.speechify.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzgcPbXJTyeBzzh8hwFNPyghGeExqlJ9SMVyv9Wlx311qTsGKy13k0fiJpw/SS93M4FFt16C6wBFk0GaEtfCVAQprOTpnBfIAvNsDs+POH/53vyGv9k84sBtQyw4ik2qTzoe9cZz96K0biXCP+63kteimP8F1Sd9E/2srtoi6Yq7wUipdASMYYCswtuZE/QUxxvSx4H3112DUmzbyNnNDuyPuEii4pvQdlDTyaOcJYBKtfh2tt6sg9pJ+WJpnhyXym4eWsABSmdkP6rIoHG69wxfSkUlEA0y99hUz2ofd0clLKo2arjCARcrFSSyzA1CtTl04dpY/RrcChX70q4OpaQIDAQAB
s2._domainkey.speechify.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDcvhS729160nQ7LwLS5aoUjQ82MvpH8HPua4wV8zFlnttCqJYz4M6taklMlnQAGuXWgDY/39zrRuPGyP1Y5/enjv4TGamqgA6PZJFKYfnH1jQfgz2C2ZX+BGTKocisorwZjbu6/bMmkUpuJtJk7x2yy58KTPvTG/7d1tlYy0W+uwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
172.67.68.119Website172.67.68.0/24
104.26.1.186Website104.26.1.0/24
104.26.0.186Website104.26.0.0/24
172.64.35.247Name server christian.ns.cloudflare.com172.64.35.0/24
172.64.34.79Name server irena.ns.cloudflare.com172.64.34.0/24
64.233.167.27Mail server aspmx.l.google.com64.233.167.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
172.253.148.27Mail 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 speechify.com

Domain Name: SPEECHIFY.COM
   Registry Domain ID: 1799887834_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.cloudflare.com
   Registrar URL: http://www.cloudflare.com
   Updated Date: 2024-07-09T04:15:39Z
   Creation Date: 2013-05-08T18:21:51Z
   Registry Expiry Date: 2031-05-08T18:21:51Z
   Registrar: Cloudflare, Inc.
   Registrar IANA ID: 1910
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.6503198930
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: CHRISTIAN.NS.CLOUDFLARE.COM
   Name Server: IRENA.NS.CLOUDFLARE.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T22:52: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.