Summary
- Registrar
- NAMECHEAP
- Status
- clientTransferProhibited
- Created on
- August 2, 2023
- Expires on
- August 2, 2027
- Name servers
- neil.ns.cloudflare.com, christina.ns.cloudflare.com
- Mail servers
- —
- DMARC
- Reject
- SPF
- Strict
- DKIM
- 1 key found
- Website
- See the website
Spoofing protection (DMARC)
E-mails spoofing this domain are rejected.
DMARC tells mail servers what to do with an e-mail that claims to come from supabase.link but fails SPF and DKIM checks.
- Policy
- Reject
- Subdomain policy
- Reject
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- —
- Failure reports
- —
Record
v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r;
Authorized senders (SPF)
E-mails sent by any other server are rejected.
SPF lists the servers allowed to send e-mails for supabase.link.
| Rule | Value | Result |
|---|---|---|
| all | — | Rejected |
Top-level DNS lookups: 0 of 10 allowed
Record
v=spf1 -all
E-mail signing (DKIM)
DKIM keys published by supabase.link under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| default | — | RSA | Revoked |
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 supabase.link arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from supabase.link 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 @supabase.link 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
supabase.link MX 10 mx1.supabase.link. supabase.link MX 20 mx2.supabase.link.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.supabase.link.
- 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
supabase.link 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.supabase.link, 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.supabase.link 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.supabase.link, 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.supabase.link 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 supabase.link
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.
| Type | IP address |
|---|---|
| A | 76.76.21.21 |
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.
| Server | IP address |
|---|---|
| neil.ns.cloudflare.com | 173.245.59.211 |
| christina.ns.cloudflare.com | 162.159.38.193 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @supabase.link 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.
No mail server: the domain does not receive e-mails.
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.supabase.link.
| Name | Content |
|---|---|
| supabase.link | v=spf1 -all |
| _dmarc.supabase.link | v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; |
| default._domainkey.supabase.link | v=DKIM1; p=; |
Related IP addresses
IPv4 addresses used by supabase.link: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 76.76.21.21 | Website | 76.76.21.0/24 |
| 173.245.59.211 | Name server neil.ns.cloudflare.com | 173.245.59.0/24 |
| 162.159.38.193 | Name server christina.ns.cloudflare.com | 162.159.38.0/24 |
WHOIS of the domain supabase.link
Domain Name: supabase.link Registry Domain ID: DO_209593b0210a7bb280d73222469106c1-UR Registrar WHOIS Server: whois.namecheap.com Registrar URL: https://www.namecheap.com Updated Date: 2026-07-08T07:25:42.248Z Creation Date: 2023-08-02T07:57:10.787Z Registry Expiry Date: 2027-08-02T07:57:10.787Z Registrar: NAMECHEAP Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.6613102107 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: christina.ns.cloudflare.com Name Server: neil.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf >>> Last update of WHOIS database: 2026-10-02T11:53:48.451Z <<< 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: supabase.link Registry Domain ID: DO_209593b0210a7bb280d73222469106c1-UR Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2026-07-03T07:23:55.07Z Creation Date: 2023-08-02T07:57:10.78Z Registrar Registration Expiration Date: 2027-08-02T07:57:10.78Z Registrar: NAMECHEAP INC Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.9854014545 Reseller: NAMECHEAP INC Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: Registrant Name: Redacted for Privacy Registrant Organization: Privacy service provided by Withheld for Privacy ehf Registrant Street: Kalkofnsvegur 2 Registrant City: Reykjavik Registrant State/Province: Capital Region Registrant Postal Code: 101 Registrant Country: IS Registrant Phone: +354.4212434 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] Registry Admin ID: Admin Name: Redacted for Privacy Admin Organization: Privacy service provided by Withheld for Privacy ehf Admin Street: Kalkofnsvegur 2 Admin City: Reykjavik Admin State/Province: Capital Region Admin Postal Code: 101 Admin Country: IS Admin Phone: +354.4212434 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: [email protected] Registry Tech ID: Tech Name: Redacted for Privacy Tech Organization: Privacy service provided by Withheld for Privacy ehf Tech Street: Kalkofnsvegur 2 Tech City: Reykjavik Tech State/Province: Capital Region Tech Postal Code: 101 Tech Country: IS Tech Phone: +354.4212434 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: [email protected] Name Server: christina.ns.cloudflare.com Name Server: neil.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-10-02T09:53:49.35Z <<< For more information on Whois status codes, please visit https://icann.org/epp % Query time: 1547 msec % WHEN: Fri Oct 02 11:53:47 UTC 2026