Summary
- Registrar
- Gandi SAS
- Status
- clientTransferProhibited
- Created on
- June 21, 2018
- Expires on
- June 21, 2027
- Name servers
- ns-1763.awsdns-28.co.uk, ns-985.awsdns-59.net, ns-1509.awsdns-60.org, ns-332.awsdns-41.com
- Mail servers
- —
- DKIM
- No key found among the common selectors
- Website
- See the website
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 bnds.us arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from bnds.us 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 @bnds.us 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
bnds.us MX 10 mx1.bnds.us. bnds.us MX 20 mx2.bnds.us.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.bnds.us.
- 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
bnds.us 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.bnds.us, 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.bnds.us 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.bnds.us, 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.bnds.us 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 bnds.us
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 | 143.204.194.114 |
| A | 143.204.194.56 |
| A | 143.204.194.46 |
| A | 143.204.194.99 |
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 |
|---|---|
| ns-1763.awsdns-28.co.uk | 205.251.198.227 |
| ns-985.awsdns-59.net | 205.251.195.217 |
| ns-1509.awsdns-60.org | 205.251.197.229 |
| ns-332.awsdns-41.com | 205.251.193.76 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @bnds.us 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.bnds.us.
| Name | Content |
|---|---|
| bnds.us | d2ryknxnlos0lt.cloudfront.net |
Related IP addresses
IPv4 addresses used by bnds.us: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 143.204.194.114 | Website | 143.204.194.0/24 |
| 143.204.194.56 | Website | 143.204.194.0/24 |
| 143.204.194.46 | Website | 143.204.194.0/24 |
| 143.204.194.99 | Website | 143.204.194.0/24 |
| 205.251.198.227 | Name server ns-1763.awsdns-28.co.uk | 205.251.198.0/24 |
| 205.251.195.217 | Name server ns-985.awsdns-59.net | 205.251.195.0/24 |
| 205.251.197.229 | Name server ns-1509.awsdns-60.org | 205.251.197.0/24 |
| 205.251.193.76 | Name server ns-332.awsdns-41.com | 205.251.193.0/24 |
WHOIS of the domain bnds.us
Domain Name: bnds.us Registry Domain ID: D01CAE4F28B664593AF8DBB83561DDC33-NSR Registrar WHOIS Server: Registrar URL: whois.gandi.net Updated Date: 2026-05-22T20:28:38Z Creation Date: 2018-06-21T20:24:32Z Registry Expiry Date: 2027-06-21T20:24:32Z Registrar: Gandi SAS Registrar IANA ID: 81 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.170377661 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: C1972A04813FA42688CDB51F1E6ED740E-NSR Registrant Name: Fabrice Sergent Registrant Organization: Bandsintown Group, Inc. Registrant Street: 2045 Biscayne Blvd, Ste 260 Registrant Street: Registrant Street: Registrant City: miami Registrant State/Province: FL Registrant Postal Code: 33137 Registrant Country: US Registrant Phone: +1.2127675267 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] Registrant Application Purpose: P1 Registrant Nexus Category: C21 Registry Admin ID: C94A10652BC8A44B3A36AA7F1B69F8D31-NSR Admin Name: Muriel Lelandais Admin Organization: Bandsintown Group, Inc. Admin Street: 2045 Biscayne Blvd, Ste 260 Admin Street: Admin Street: Admin City: miami Admin State/Province: FL Admin Postal Code: 33137 Admin Country: US Admin Phone: +1.2127675267 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: [email protected] Admin Application Purpose: P1 Admin Nexus Category: C21 Registry Tech ID: CDEC16DEC63224CBAA35EAE5A001FB953-NSR Tech Name: Michael Reiczyk Tech Organization: Bandsintown Group, Inc. Tech Street: 2045 Biscayne Blvd, Ste 260 Tech Street: Tech Street: Tech City: miami Tech State/Province: FL Tech Postal Code: 33137 Tech Country: US Tech Phone: +1.5142885858 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: [email protected] Tech Application Purpose: P1 Tech Nexus Category: C21 Name Server: ns-70.awsdns-08.com Name Server: ns-1465.awsdns-55.org Name Server: ns-1968.awsdns-54.co.uk Name Server: ns-986.awsdns-59.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T20:33:28Z <<< For more information on Whois status codes, please visit https://icann.org/epp .US WHOIS Complaint Tool - http://www.whoiscomplaints.us Advanced WHOIS Instructions - http://whois.us/help.html Registry Services, LLC, the Registry Administrator for .US, has collected this information for the WHOIS database through a .US-Accredited Registrar. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the registry database. Registry Services, LLC makes this information available to you "as is" and does not guarantee 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: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without our prior written permission. We reserve the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.whois.us. % Query time: 592 msec % WHEN: Thu Oct 01 20:33:27 UTC 2026