Summary
- Registrar
- Webnames.ca Inc.
- Status
- clientTransferProhibited
- Created on
- October 12, 2012
- Expires on
- October 12, 2027
- Name servers
- a10-65.akam.net, a26-66.akam.net, a4-67.akam.net, a1-62.akam.net, a5-64.akam.net, a7-65.akam.net
- Mail servers
- —
- DMARC
- Reject
- SPF
- Strict
- DKIM
- No key found among the common selectors
- 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 bncd.ca but fails SPF and DKIM checks.
- Policy
- Reject
- Subdomain policy
- Reject
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- [email protected]
- Failure reports
- [email protected]
Record
v=DMARC1;p=reject;rua=mailto:[email protected];ruf=mailto:[email protected];fo=0
Authorized senders (SPF)
E-mails sent by any other server are rejected.
SPF lists the servers allowed to send e-mails for bncd.ca.
| Rule | Value | Result |
|---|---|---|
| all | — | Rejected |
Top-level DNS lookups: 0 of 10 allowed
Record
v=spf1 -all
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 bncd.ca arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from bncd.ca 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 @bncd.ca 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
bncd.ca MX 10 mx1.bncd.ca. bncd.ca MX 20 mx2.bncd.ca.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.bncd.ca.
- 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
bncd.ca 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.bncd.ca, 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.bncd.ca 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.bncd.ca, 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.bncd.ca 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 bncd.ca
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 | 96.17.193.46 |
| A | 96.17.193.20 |
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 |
|---|---|
| a10-65.akam.net | 96.7.50.65 |
| a26-66.akam.net | 23.74.25.66 |
| a4-67.akam.net | 72.246.46.67 |
| a1-62.akam.net | 193.108.91.62 |
| a5-64.akam.net | 95.100.168.64 |
| a7-65.akam.net | 23.61.199.65 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @bncd.ca 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.bncd.ca.
| Name | Content |
|---|---|
| bncd.ca | _globalsign-domain-verification=caSD2AsXZAtf1sxi_SewWi4NWIjk0K9SXdmiUCN_Di |
| bncd.ca | _globalsign-domain-verification=p2ir28riFbzCqPdfa-AQ2_luBfg3mQ2XQRuJ0qcPeZ |
| bncd.ca | _globalsign-domain-verification=6y7FT1PzoIF7gBVy2_D2QbcjRx3V3nf4-iJaKT9okJ |
| bncd.ca | facebook-domain-verification=swi1ukvahujydl19iexnazkiip4sdf |
| bncd.ca | google-site-verification=MhURAjxKTW8MqNSxbS4l_F_jbqad_cmtahsxstjuI9I |
| bncd.ca | v=spf1 -all |
| bncd.ca | globalsign-domain-verification=D4D5F4FB48B25468AFEDF4D9AC96DA49 |
| _dmarc.bncd.ca | v=DMARC1;p=reject;rua=mailto:[email protected];ruf=mailto:[email protected];fo=0 |
Related IP addresses
IPv4 addresses used by bncd.ca: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 96.17.193.46 | Website | 96.17.193.0/24 |
| 96.17.193.20 | Website | 96.17.193.0/24 |
| 96.7.50.65 | Name server a10-65.akam.net | 96.7.50.0/24 |
| 23.74.25.66 | Name server a26-66.akam.net | 23.74.25.0/24 |
| 72.246.46.67 | Name server a4-67.akam.net | 72.246.46.0/24 |
| 193.108.91.62 | Name server a1-62.akam.net | 193.108.91.0/24 |
| 95.100.168.64 | Name server a5-64.akam.net | 95.100.168.0/24 |
| 23.61.199.65 | Name server a7-65.akam.net | 23.61.199.0/24 |
WHOIS of the domain bncd.ca
Domain Name: bncd.ca Registry Domain ID: 6582640-CIRA Registrar WHOIS Server: whois.ca.fury.ca Registrar URL: webnames.ca Updated Date: 2026-09-28T21:36:24Z Creation Date: 2012-10-12T21:06:22Z Registry Expiry Date: 2027-10-12T21:06:22Z Registrar: Webnames.ca Inc. Registrar IANA ID: 456 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.8662217878 Registrar Abuse Contact Phone Ext: Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: R605833-CIRA Registrant Name: Webnames Private Registrant Organization: Webnames Services INC Registrant Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Registrant City: Coquitlam Registrant State/Province: BC Registrant Postal Code: V3B6B4 Registrant Country: CA Registrant Phone: +1.6046331142 Registrant Phone Ext: Registrant Fax: +1.2064562714 Registrant Fax Ext: Registrant Email: [email protected] Registry Admin ID: C1973214-CIRA Admin Name: Webnames Private Admin Organization: Webnames Services INC Admin Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Admin City: Coquitlam Admin State/Province: BC Admin Postal Code: V3B6B4 Admin Country: CA Admin Phone: +1.6046331142 Admin Phone Ext: Admin Fax: +1.2064562714 Admin Fax Ext: Admin Email: [email protected] Registry Tech ID: 29239175-CIRA Tech Name: Webnames Private Tech Organization: Webnames Services INC Tech Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Tech City: Coquitlam Tech State/Province: BC Tech Postal Code: V3B6B4 Tech Country: CA Tech Phone: +1.6046331142 Tech Phone Ext: Tech Fax: +1.2064562714 Tech Fax Ext: Tech Email: [email protected] Registry Billing ID: Billing Name: Billing Organization: Billing Street: Billing City: Billing State/Province: Billing Postal Code: Billing Country: Billing Phone: Billing Phone Ext: Billing Fax: Billing Fax Ext: Billing Email: Name Server: a1-62.akam.net Name Server: a10-65.akam.net Name Server: a26-66.akam.net Name Server: a4-67.akam.net Name Server: a5-64.akam.net Name Server: a7-65.akam.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-02T16:48:11Z <<< For more information on Whois status codes, please visit https://icann.org/epp % % Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal % Notice, available at https://www.cira.ca/en/resources/documents/about/website-terms-use % % (c) 2026 Canadian Internet Registration Authority, (http://www.cira.ca/) Domain Name: bncd.ca Registry Domain ID: 6582640-CIRA Registrar WHOIS Server: whois.ca.fury.ca Registrar URL: webnames.ca Updated Date: 2026-09-28T21:36:24Z Creation Date: 2012-10-12T21:06:22Z Registry Expiry Date: 2027-10-12T21:06:22Z Registrar: Webnames.ca Inc. Registrar IANA ID: 456 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.8662217878 Registrar Abuse Contact Phone Ext: Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: R605833-CIRA Registrant Name: Webnames Private Registrant Organization: Webnames Services INC Registrant Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Registrant City: Coquitlam Registrant State/Province: BC Registrant Postal Code: V3B6B4 Registrant Country: CA Registrant Phone: +1.6046331142 Registrant Phone Ext: Registrant Fax: +1.2064562714 Registrant Fax Ext: Registrant Email: [email protected] Registry Admin ID: C1973214-CIRA Admin Name: Webnames Private Admin Organization: Webnames Services INC Admin Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Admin City: Coquitlam Admin State/Province: BC Admin Postal Code: V3B6B4 Admin Country: CA Admin Phone: +1.6046331142 Admin Phone Ext: Admin Fax: +1.2064562714 Admin Fax Ext: Admin Email: [email protected] Registry Tech ID: 29239175-CIRA Tech Name: Webnames Private Tech Organization: Webnames Services INC Tech Street: ATTN: WN3a559f, Suite 260 - 3020 Lincoln Ave. Tech City: Coquitlam Tech State/Province: BC Tech Postal Code: V3B6B4 Tech Country: CA Tech Phone: +1.6046331142 Tech Phone Ext: Tech Fax: +1.2064562714 Tech Fax Ext: Tech Email: [email protected] Registry Billing ID: Billing Name: Billing Organization: Billing Street: Billing City: Billing State/Province: Billing Postal Code: Billing Country: Billing Phone: Billing Phone Ext: Billing Fax: Billing Fax Ext: Billing Email: Name Server: a1-62.akam.net Name Server: a10-65.akam.net Name Server: a26-66.akam.net Name Server: a4-67.akam.net Name Server: a5-64.akam.net Name Server: a7-65.akam.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-02T16:48:12Z <<< For more information on Whois status codes, please visit https://icann.org/epp % % Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal % Notice, available at https://www.cira.ca/en/resources/documents/about/website-terms-use % % (c) 2026 Canadian Internet Registration Authority, (http://www.cira.ca/) % Query time: 735 msec % WHEN: Fri Oct 02 16:48:11 UTC 2026