Dataweaz

neon.tech

Summary

Registrar
MarkMonitor Inc.
Status
clientUpdateProhibited
Created on
April 6, 2022
Expires on
April 7, 2028
Name servers
novalee.ns.cloudflare.com, kobe.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

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 neon.tech but fails SPF and DKIM checks.

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

Record

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

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for neon.tech.

RuleValueResult
include_spf.google.comAllowed
includeamazonses.comAllowed
include26233105.spf04.hubspotemail.netAllowed
includemail.zendesk.comAllowed
all—Rejected

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 include:_spf.google.com include:amazonses.com include:26233105.spf04.hubspotemail.net include:mail.zendesk.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 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 neon.tech arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from neon.tech 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 @neon.tech 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

neon.tech  MX  10 mx1.neon.tech.
neon.tech  MX  20 mx2.neon.tech.

What the record contains

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

neon.tech  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.neon.tech, 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.neon.tech  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.neon.tech, 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.neon.tech  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 neon.tech

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
A104.18.22.51
A104.18.23.51
AAAA2606:4700::6812:1733
AAAA2606:4700::6812:1633

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
novalee.ns.cloudflare.com162.159.38.182
kobe.ns.cloudflare.com108.162.195.193

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @neon.tech 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.com108.177.15.27
5alt1.aspmx.l.google.com192.178.213.26
5alt2.aspmx.l.google.com172.253.148.27
10alt3.aspmx.l.google.com142.250.147.27
10alt4.aspmx.l.google.com172.253.152.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.neon.tech.

NameContent
neon.technotion-domain-verification=EPkDFDaEN652Tjkel1LS2mE61tRsvbnbruhJtwHTIUx
neon.techsegment-site-verification=xZFlg2pTRj78c2llKohIYuSpWtHeb2dx
neon.techv=spf1 include:_spf.google.com include:amazonses.com include:26233105.spf04.hubspotemail.net include:mail.zendesk.com -all
neon.techMS=11EE64208FAC21EE7FE22052BB9FF3996902AFA1
neon.techMS=ms75740097
neon.techapple-domain-verification=51pISUJvRWMK4dAg
neon.techdocker-verification=11390bbd-895a-4e80-baf5-5703218ec517
neon.techgoogle-site-verification=AdXLmRNoLhkhGUixRJJtxb2XR50Jf-ojfTNK51avphc
neon.techgoogle-site-verification=OxwqnZ5U7yXwcUKdQsppCKvd3Vy2Dfm4ndJ2O5uJEQk
neon.techgoogle-site-verification=Qyqz7CD_Zp2FX58jlmyXLiUm8VgUYqeH8J891-sRLws
neon.techgoogle-site-verification=tM8JjH16_1AHnWGx7K79HRi7drReSub4lca0PalU2nY
neon.techh1-domain-verification=5X1vKFBcM847gzMuL1cf8RaM8D935iEBhMZq2zt8mPwiinad
_dmarc.neon.techv=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]
google._domainkey.neon.techv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1qOnDzphtpkeNkdGdefYfJGCVf1zkIkv6kyHjbJEalnAULq5fJ7Q2pHZlyLIiR5X0cZM6KvyxhZLgStaoubDt/cxwJxOsmgOgJjjD5KK+SbX8UgnG2LuHPWn0619Hg44hwIlowI7FdECBURJcOE8r/+BT0c0ZbFkG49MFAFNbfQIDAQAB

Related IP addresses

IPv4 addresses used by neon.tech: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
104.18.22.51Website104.18.22.0/24
104.18.23.51Website104.18.23.0/24
162.159.38.182Name server novalee.ns.cloudflare.com162.159.38.0/24
108.162.195.193Name server kobe.ns.cloudflare.com108.162.195.0/24
108.177.15.27Mail server aspmx.l.google.com108.177.15.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.27Mail server alt2.aspmx.l.google.com172.253.148.0/24
142.250.147.27Mail server alt3.aspmx.l.google.com142.250.147.0/24
172.253.152.27Mail server alt4.aspmx.l.google.com172.253.152.0/24

WHOIS of the domain neon.tech

Domain Name: neon.tech
Registry Domain ID: D288781654-CNIC
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: https://www.markmonitor.com/
Updated Date: 2025-09-17T15:17:23.000Z
Creation Date: 2022-04-06T16:58:49.000Z
Registry Expiry Date: 2028-04-06T23:59:59.000Z
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Name Server: kobe.ns.cloudflare.com
Name Server: novalee.ns.cloudflare.com
DNSSEC: signedDelegation
URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

>>> Last update of WHOIS database: 2026-10-01T15:49:30.257Z <<<

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

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Tucows Registry for informational
purposes only, and it does not guarantee its accuracy. Tucows Registry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Tucows Registry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass  unsolicited, commercial advertising
or solicitations to entities other than your existing  customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Tucows Registry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.
Domain Name: neon.tech
Registry Domain ID: D288781654-CNIC
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2026-03-23T18:00:22+0000
Creation Date: 2022-04-06T16:58:49+0000
Registrar Registration Expiration Date: 2028-04-06T23:59:59+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact: https://corp.markmonitor.com/domain/ui/abuse-report
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: Databricks Inc.
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/neon.tech
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/neon.tech
Name Server: kobe.ns.cloudflare.com
Name Server: novalee.ns.cloudflare.com
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T15:49:30+0000 <<<

For more information on WHOIS status codes, please visit:
  https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
  https://domains.markmonitor.com/whois/contact/neon.tech

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to [email protected]
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will 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 by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
  (2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220

% Query time: 1024 msec
% WHEN: Thu Oct 01 15:49:29 UTC 2026