syntax.fm - DNS, WHOIS, DMARC and SPF of the domain name

Summary

Registrar: Gandi SAS
Status: clientTransferProhibited
Created on: May 21, 2016
Expires on: May 21, 2027
Name servers: olga.ns.cloudflare.com, dane.ns.cloudflare.com
Mail servers: aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
DMARC: Quarantine
SPF: Soft
DKIM: 1 key found
Website: See the website

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

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

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

Record

v=DMARC1; p=quarantine; fo=1; aspf=r; pct=100; rua=mailto:[email protected]; ruf=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 syntax.fm.

Rule	Value	Result
include	_spf.google.com	Allowed
all	—	Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:_spf.google.com ~all

E-mail signing (DKIM)

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

Selector	Likely service	Key	Status
google	Google Workspace	RSA 2048 bits	Active

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

syntax.fm  MX  10 mx1.syntax.fm.
syntax.fm  MX  20 mx2.syntax.fm.

What the record contains

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

syntax.fm  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.syntax.fm, 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.syntax.fm  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.syntax.fm, 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.syntax.fm  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 syntax.fm

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	172.67.134.109
A	104.21.25.175
AAAA	2606:4700:3035::6815:19af
AAAA	2606:4700:3037::ac43:866d

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
olga.ns.cloudflare.com	108.162.192.137
dane.ns.cloudflare.com	108.162.193.97

Mail servers (MX)

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

Priority	Server	IP address
1	aspmx.l.google.com	64.233.166.27
5	alt2.aspmx.l.google.com	142.251.127.26
5	alt1.aspmx.l.google.com	192.178.213.26
10	alt4.aspmx.l.google.com	142.250.147.26
10	alt3.aspmx.l.google.com	172.253.148.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.syntax.fm.

Name	Content
syntax.fm	notion-domain-verification=c90gqLGTtH5azwbylNNVgf8QocPxulnPuF2FfGWfviB
syntax.fm	v=spf1 include:_spf.google.com ~all
syntax.fm	google-site-verification=ZldP3lc4IYS37KhXCZEifaJivJjV2Op-LbjDpPhX4q8
syntax.fm	google-site-verification=zqEgJtpD7Af2x759_0TF1CQ_hjVJKxA3YG3sfsfu43Y
_dmarc.syntax.fm	v=DMARC1; p=quarantine; fo=1; aspf=r; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected];
google._domainkey.syntax.fm	v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgIP68Gm9oVYd/CwDY4QTtx2fgl2d6+E5TwQfmaqS3RA2bIyaKk99B90RCVIeapyRIVgQQWIp1iOxPDxk7s6uoa0mqScsLs2VUTZ0874NtbXbEUE9SjWXmCGZ379m4ZHnpTH1a4onvcRvRisyBVegK2FlyFIHzg8ID8IBGkjiRliDTNs9bA58euVQDDKsr7H+AWzW4ArM/SIFFQBYIAZjn9dpOYgTsa7Sy9NlFeULCFCcwLrUE9dkz7Xmc4B2P63GnXeCEIv/Kr0YQ7dVRS3jiCe1vRZXQMNdSlW837hmIKBO/0AmxY8GfVMRd77JdkL0/hZXq735yBoTVVHwinz1WwIDAQAB

Related IP addresses

IPv4 addresses used by syntax.fm: website, name servers, mail servers and senders authorized by SPF.

IP address	Used for	/24 block
172.67.134.109	Website	172.67.134.0/24
104.21.25.175	Website	104.21.25.0/24
108.162.192.137	Name server olga.ns.cloudflare.com	108.162.192.0/24
108.162.193.97	Name server dane.ns.cloudflare.com	108.162.193.0/24
64.233.166.27	Mail server aspmx.l.google.com	64.233.166.0/24
142.251.127.26	Mail server alt2.aspmx.l.google.com	142.251.127.0/24
192.178.213.26	Mail server alt1.aspmx.l.google.com	192.178.213.0/24
142.250.147.26	Mail server alt4.aspmx.l.google.com	142.250.147.0/24
172.253.148.26	Mail server alt3.aspmx.l.google.com	172.253.148.0/24

WHOIS of the domain syntax.fm

Domain Name: SYNTAX.FM
Registry Domain ID: D34917164-CNIC
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net/
Updated Date: 2026-06-02T16:52:24.0Z
Creation Date: 2016-05-20T23:59:59.0Z
Registry Expiry Date: 2027-05-20T23:59:59.0Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Email: https://whois.nic.fm/contact/syntax.fm/registrant
Tech Email: https://whois.nic.fm/contact/syntax.fm/tech
Name Server: DANE.NS.CLOUDFLARE.COM
Name Server: OLGA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.170377661
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-02T07:38:25.0Z <<<

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

The registration data available in this service is limited. Additional
data may be available at https://lookup.icann.org

The Whois and RDAP services are provided by CentralNic, and contain
information pertaining to Internet domain names registered by our
our customers. By using this service you are agreeing (1) not to use any
information presented here for any purpose other than determining
ownership of domain names, (2) not to store or reproduce this data in
any way, (3) not to use any high-volume, automated, electronic processes
to obtain data from this service. Abuse of this service is monitored and
actions in contravention of these terms will result in being permanently
blacklisted. All data is (c) CentralNic Ltd (https://www.centralnicregistry.com)

Access to the Whois and RDAP services is rate limited. For more
information, visit https://centralnicregistry.com/policies/whois-guidance.
Domain Name: syntax.fm
Registry Domain ID: D34917164-CNIC
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2026-04-19T21:33:04Z
Creation Date: 2016-05-20T21:59:59Z
Registrar Registration Expiration Date: 2027-05-20T23:59:59Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.170377661
Reseller: 
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: 
Domain Status: 
Domain Status: 
Domain Status: 
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Functional Software, Inc dba Sentry
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: California
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: [email protected]
Name Server: DANE.NS.CLOUDFLARE.COM
Name Server: OLGA.NS.CLOUDFLARE.COM
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-02T07:38:25Z <<<

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

Reseller Email: 
Reseller URL: 

Personal data access and use are governed by French law, any use for the purpose of unsolicited mass commercial advertising as well as any mass or automated inquiries (for any intent other than the registration or modification of a domain name) are strictly forbidden. Copy of whole or part of our database without Gandi's endorsement is strictly forbidden.
A dispute over the ownership of a domain name may be subject to the alternate procedure established by the Registry in question or brought before the courts.
For additional information, please contact us via the following form:
 https://www.gandi.net/support/contacter/mail/

% Query time: 503 msec
% WHEN: Fri Oct 02 07:38:25 UTC 2026