Dataweaz

hoverair.com

Summary

Registrar
Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
Status
ok
Created on
August 22, 2012
Expires on
August 22, 2027
Name servers
simone.ns.cloudflare.com, trey.ns.cloudflare.com
Mail servers
mx1.feishu.cn, mx2.feishu.cn, mx3.feishu.cn
DMARC
Monitoring
SPF
Soft
DKIM
3 keys found
Website
See the website

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

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

Record

v=DMARC1; p=none; 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 hoverair.com.

RuleValueResult
ip410.130.122.0/23Allowed
ip4146.20.112.0/26Allowed
ip4161.38.192.0/20Allowed
ip4143.55.224.0/21Allowed
ip4143.55.232.0/22Allowed
ip4159.112.240.0/20Allowed
ip4198.244.48.0/20Allowed
ip4204.220.168.0/21Allowed
ip4204.220.176.0/20Allowed
ip4141.193.32.0/23Allowed
ip4159.135.140.80/29Allowed
ip4159.135.132.128/25Allowed
ip4161.38.204.0/22Allowed
ip487.253.232.0/21Allowed
ip4185.189.236.0/22Allowed
ip4185.211.120.0/22Allowed
ip4185.250.236.0/22Allowed
ip4143.55.236.0/22Allowed
ip4198.244.6.0/22Allowed
ip4204.220.160.0/21Allowed
ip4199.255.192.0/22Allowed
ip4199.127.232.0/22Allowed
ip454.240.0.0/18Allowed
ip469.169.224.0/20Allowed
ip423.249.208.0/20Allowed
ip423.251.224.0/19Allowed
ip476.223.176.0/20Allowed
ip454.240.64.0/18Allowed
ip476.223.128.0/19Allowed
ip4216.221.16.0/19Allowed
ip4206.55.144.0/20Allowed
ip4216.198.0.0/18Allowed
ip4115.124.21.0/24Allowed
ip4140.205.208.0/24Allowed
ip4140.205.210.0/24Allowed
ip447.88.45.0/24Allowed
ip48.219.35.0/24Allowed
ip447.90.196.0/24Allowed
ip4106.11.171.128/25Allowed
ip48.221.26.0/23Allowed
ip48.221.28.0/22Allowed
ip4115.124.24.0/24Allowed
ip48.219.7.128/25Allowed
ip48.221.30.128/25Allowed
ip447.245.196.128/25Allowed
ip44.110.64.0/18Allowed
ip4209.61.151.0/24Allowed
ip4166.78.68.0/22Allowed
ip4198.61.254.0/23Allowed
ip4192.237.158.0/23Allowed
ip423.253.18.0/23Allowed
ip4104.130.96.0/28Allowed
ip4146.20.113.0/24Allowed
ip4146.20.191.0/24Allowed
ip4159.135.224.0/20Allowed
ip469.72.32.0/20Allowed
ip4209.127.230.0/23Allowed
ip4103.149.242.0/24Allowed
ip4101.36.218.0/24Allowed
ip4118.26.13.0/24Allowed
ip471.18.227.0/24Allowed
ip4101.45.255.0/24Allowed
ip4159.112.246.20/30Allowed
ip4159.112.246.24/31Allowed
ip4143.55.235.30/31Allowed
ip469.72.33.5Allowed
ip469.72.33.234Allowed
ip454.240.44.207Allowed
ip454.240.44.208Allowed
ip454.240.45.76/30Allowed
ip454.240.45.80/30Allowed
ip4185.249.220.0/24Allowed
ip4185.225.161.0/24Allowed
ip4103.151.192.0/23Allowed
ip4185.12.80.0/22Allowed
ip4188.172.128.0/20Allowed
ip4192.161.144.0/20Allowed
all—Suspicious

Top-level DNS lookups: 0 of 10 allowed

Record

v=spf1 ip4:10.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.6.0/22 ip4:204.220.160.0/21 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.16.0/19 ip4:206.55.144.0/20 ip4:216.198.0.0/18 ip4:115.124.21.0/24 ip4:140.205.208.0/24 ip4:140.205.210.0/24 ip4:47.88.45.0/24 ip4:8.219.35.0/24 ip4:47.90.196.0/24 ip4:106.11.171.128/25 ip4:8.221.26.0/23 ip4:8.221.28.0/22 ip4:115.124.24.0/24 ip4:8.219.7.128/25 ip4:8.221.30.128/25 ip4:47.245.196.128/25 ip4:4.110.64.0/18 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.18.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:209.127.230.0/23 ip4:103.149.242.0/24 ip4:101.36.218.0/24 ip4:118.26.13.0/24 ip4:71.18.227.0/24 ip4:101.45.255.0/24 ip4:159.112.246.20/30 ip4:159.112.246.24/31 ip4:143.55.235.30/31 ip4:69.72.33.5 ip4:69.72.33.234 ip4:54.240.44.207 ip4:54.240.44.208 ip4:54.240.45.76/30 ip4:54.240.45.80/30 ip4:185.249.220.0/24 ip4:185.225.161.0/24 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
mail—RSA 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 hoverair.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from hoverair.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 @hoverair.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

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

hoverair.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.hoverair.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.hoverair.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.hoverair.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.hoverair.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 hoverair.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
A23.227.38.74
AAAA2620:127:f00f:e::

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
simone.ns.cloudflare.com108.162.194.26
trey.ns.cloudflare.com172.64.33.242

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @hoverair.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
1mx1.feishu.cn52.220.106.220
5mx2.feishu.cn122.14.229.0
10mx3.feishu.cn101.126.58.225

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

NameContent
hoverair.comgoogle-site-verification=-2TmHMare-lM-CyJOZwvCdf8k_u5Kultua28JlvyfOE
hoverair.combrevo-code:060037eab5a09cf8f121bbc534160e4f
hoverair.combrevo-code:e95e179a214b0ed38a5335e6720bac72
hoverair.combrevo-code:b0940e7924bfe3573b2ffc140c162fee
hoverair.combrevo-code:22852381c9561caa3ffd0f93bb1caeff
hoverair.comverification-code-site-App_feishu=8mLitOkno9eAfObvRegL
hoverair.combrevo-code:e3729f002b23253c7584e5deac652c22
hoverair.comv=spf1 ip4:10.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.6.0/22 ip4:204.220.160.0/21 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.16.0/19 ip4:206.55.144.0/20 ip4:216.198.0.0/18 ip4:115.124.21.0/24 ip4:140.205.208.0/24 ip4:140.205.210.0/24 ip4:47.88.45.0/24 ip4:8.219.35.0/24 ip4:47.90.196.0/24 ip4:106.11.171.128/25 ip4:8.221.26.0/23 ip4:8.221.28.0/22 ip4:115.124.24.0/24 ip4:8.219.7.128/25 ip4:8.221.30.128/25 ip4:47.245.196.128/25 ip4:4.110.64.0/18 ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.18.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:209.127.230.0/23 ip4:103.149.242.0/24 ip4:101.36.218.0/24 ip4:118.26.13.0/24 ip4:71.18.227.0/24 ip4:101.45.255.0/24 ip4:159.112.246.20/30 ip4:159.112.246.24/31 ip4:143.55.235.30/31 ip4:69.72.33.5 ip4:69.72.33.234 ip4:54.240.44.207 ip4:54.240.44.208 ip4:54.240.45.76/30 ip4:54.240.45.80/30 ip4:185.249.220.0/24 ip4:185.225.161.0/24 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ~all
hoverair.combrevo-code:a0a2b3d7d4f250d36f45a3fc36a9849a
_dmarc.hoverair.comv=DMARC1; p=none; rua=mailto:[email protected]
k2._domainkey.hoverair.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.hoverair.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
mail._domainkey.hoverair.comk=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
23.227.38.74Website23.227.38.0/24
108.162.194.26Name server simone.ns.cloudflare.com108.162.194.0/24
172.64.33.242Name server trey.ns.cloudflare.com172.64.33.0/24
52.220.106.220Mail server mx1.feishu.cn52.220.106.0/24
122.14.229.0Mail server mx2.feishu.cn122.14.229.0/24
101.126.58.225Mail server mx3.feishu.cn101.126.58.0/24
69.72.33.5Authorized by SPF69.72.33.0/24
69.72.33.234Authorized by SPF69.72.33.0/24
54.240.44.207Authorized by SPF54.240.44.0/24
54.240.44.208Authorized by SPF54.240.44.0/24

WHOIS of the domain hoverair.com

Domain Name: HOVERAIR.COM
   Registry Domain ID: 1740076319_DOMAIN_COM-VRSN
   Registrar WHOIS Server: grs-whois.hichina.com
   Registrar URL: http://wanwang.aliyun.com
   Updated Date: 2026-07-04T02:22:57Z
   Creation Date: 2012-08-21T22:43:28Z
   Registry Expiry Date: 2027-08-21T22:43:28Z
   Registrar: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
   Registrar IANA ID: 1599
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +86.95187
   Domain Status: ok https://icann.org/epp#ok
   Name Server: SIMONE.NS.CLOUDFLARE.COM
   Name Server: TREY.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-02T21:59: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.