Dataweaz

500.co

Summary

Registrar
—
Status
Created on
—
Expires on
—
Name servers
ns4.dnsimple.com, ns1.dnsimple.com, ns3.dnsimple.com, ns2.dnsimple.com
Mail servers
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
SPF
Soft

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 500.co but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=quarantine; sp=none; rua=mailto:[email protected]; pct=100

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 500.co.

RuleValueResult
mx—Allowed
includesendgrid.netAllowed
include_spf.google.comAllowed
includeservers.mcsv.netAllowed
include_spf.salesforce.comAllowed
includespf.sendinblue.comAllowed
includespf.tipalti.comAllowed
includeaspmx.pardot.comAllowed
include698640.spf10.hubspotemail.netAllowed
all—Suspicious

Top-level DNS lookups: 9 of 10 allowed

Record

v=spf1 mx include:sendgrid.net include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:spf.sendinblue.com include:spf.tipalti.com include:aspmx.pardot.com include:698640.spf10.hubspotemail.net ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
k1MailchimpRSA 1024 bits · shortActive
mandrillMandrillRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive
mail—RSA 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 500.co arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from 500.co 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 @500.co 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

500.co  MX  10 mx1.500.co.
500.co  MX  20 mx2.500.co.

What the record contains

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

500.co  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.500.co, 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.500.co  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.500.co, 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.500.co  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 500.co

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
A76.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.

ServerIP address
ns4.dnsimple.com199.247.155.53
ns1.dnsimple.com199.247.152.53
ns3.dnsimple.com199.247.154.53
ns2.dnsimple.com199.247.153.53

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @500.co 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.com74.125.206.26
5alt1.aspmx.l.google.com192.178.213.27
5alt2.aspmx.l.google.com142.251.127.27
10alt4.aspmx.l.google.com142.250.147.27
10alt3.aspmx.l.google.com172.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.500.co.

NameContent
500.coslack-domain-verification=1geYcUe7gGK6xumq9MitK7r2yElL5PA3Spuyum1F
500.cov=spf1 mx include:sendgrid.net include:_spf.google.com include:servers.mcsv.net include:_spf.salesforce.com include:spf.sendinblue.com include:spf.tipalti.com include:aspmx.pardot.com include:698640.spf10.hubspotemail.net ~all
500.cozapier-domain-verification-challenge=4d7cf9f6-dc6c-46f1-881e-8883bd75c822
500.co00D4W000005j2h4=1TBUt00000000Mb
500.co802j1hh1h7u71og38jn8pk2m7q
500.coMS=ms50217208
500.coSendinblue-code:9ec3dcaa8de339f612efbc5178b9f95e
500.coanthropic-domain-verification-qcxqte=ctiq4K988k8DGcGx95E0Gm4Nw
500.coatlassian-domain-verification=/qaux0qODxLUdl2Sy1iNlPukiqGgGxpKb9BxYO7S3X8bYJrOLjRYH4/MR/QbaDRa
500.coatlassian-sending-domain-verification=5fa5c0da-bc3e-4a0f-a81d-be5f67c4de79
500.cocanva-domain-verify=052eff73-eff7-473f-bdff-6ed8ed5fa7c5
500.cocanva-site-verification=CkYBe8qhBO0ZliqGL7SvTg
500.cocoda-verification=0c7817e3-3e45-49be-b32c-6ae5dd571c95
500.codropbox-domain-verification=a5pf6l8lk50o
500.cogoogle-site-verification=cxBTsDwJh8sis5BiGIK2HHtR-lRD90-r_eVcTP6Y0Xw
500.cogoogle-site-verification=qB_-0kFiZVJbgId3oNlC0ErokaUxb9IXn6-kf0b9K_I
500.coopenai-domain-verification=dv-RB6eYvRtmafSgeVPWSxhstzY
500.coqDzrmTPnm8iGNbwTDWKfgt4nz67.@P
500.cosending_domain1076052=fef0ef474ca893bbe3bab3f385befca9c39e8e0b512e62775b014c91212bf342
500.cotwilio-domain-verification=aa9bd4338e4727e2ae2544319a8e51aa
500.co1password-site-verification=ZALGSLLYWVDUVH3ET6NRDV64HE
500.cogoogle-site-verification=oaO51kyQ1m51K06jTqnyHXGFyLxU95_8QvHrGu2m0FY
500.co5482A6FCE5
500.coZOOM_verify_Iu05MfwriVSwwnM4ywN5m2
500.coadobe-idp-site-verification=ab2f8fa85ea6a1f91b4bb13b7e98bd01ae9daa7b48bf49fcf43a5c49feb2422f
500.cobox-domain-verification=7e40ce4e68457de70596b7af447972d97be2cc4a78c68791cb347f8094966ebd
500.cocloudflare_dashboard_sso=569adf1cac787154448fc8df56014eb9
500.cohubspot-domain-verification=OWI0Y2NkZWItZmI2NS00Mzk0LTkxZGItNjJiZmYzMTk2MDUy
_dmarc.500.cov=DMARC1; p=quarantine; sp=none; rua=mailto:[email protected]; pct=100
google._domainkey.500.cov=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCBUQ3tJRm8dHlFJwNKaT03BFJWmrFCoGt9kRHY2uTQoXG0B0dsnH99uTL9njLCrPvYAD831q2VcKAvH/fMpZekdJcRH02MdILkT1IDlqGhI8nw2JNWT/rflbWyq0CdwyHQJvNDQVLAfO4cc+ArsSop3kmQDeh6OR2WEV5pyvihPwIDAQAB
k1._domainkey.500.cok=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
mandrill._domainkey.500.cov=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey.500.cok=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwGFp0oiDEZRdCnehojg9+hlsOF0BQAJxRtFAQvS6QoRg8h6SBIQmBmBSuIpN0nkJBMwPc2/pFjqi2clhNJGi2uwcpE49BX9JFzqbglQfpB+0sfAqF+tUwh8AIYQDL3Grnf2y0c3zPb+TzOZ77Hnprc9XrOLvQ5Wt1xTZ8mMPACqKujlrdKXvUQhVjHuS/JoK8Jv9pPaMXduAqnYPnCc+hpQTHeFCINb8sOkbg4o7hpHYNaLsJR4KuA9INYwGwrl0RIwBVSMJX/E7ikarFdlx3vAB/Cc/ce5Tj8frTdrmct6ZuzAsQKBCWqbFPxDir6Gp/VcC4USNgK7T5r3SiSskDQIDAQAB
s2._domainkey.500.cok=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0sILc/n+k8IPYPbN1VPQCgoc4o4gyaqgLJAv73yCd+kzEaUnqYmkwykBlAGhDpoAzL4qotnrwaO5850WL8OJMvOQ9VkqcYOtd84yEG0xgW0AX7Y4u+05fgGUZxL3R2mMQ+7QSxdml4t9qxF1L5ePFtVcAvX7oG2EONts1nRAHkeaio/RxxDxBdRHy6S/2/AAedvCXFHUNyTQ5jO+d23N6mQGlldsAfVqrkuxZ/fkbMbbSC9Ezr+PKf+5Bcn6qfba7UCEHw7Wikyjse1Q1avbg20gjrP1LwXbtn1kXB6AaD2AN4bbiIxylbKzaiUvUAiQfmL4g+yjyheoCrESoaeMUQIDAQAB
mail._domainkey.500.cok=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB

Related IP addresses

IPv4 addresses used by 500.co: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
76.76.21.21Website76.76.21.0/24
199.247.155.53Name server ns4.dnsimple.com199.247.155.0/24
199.247.152.53Name server ns1.dnsimple.com199.247.152.0/24
199.247.154.53Name server ns3.dnsimple.com199.247.154.0/24
199.247.153.53Name server ns2.dnsimple.com199.247.153.0/24
74.125.206.26Mail server aspmx.l.google.com74.125.206.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com142.251.127.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24
172.253.148.26Mail server alt3.aspmx.l.google.com172.253.148.0/24

WHOIS of the domain 500.co