Dataweaz

zendesk.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
May 16, 2005
Expires on
May 16, 2027
Name servers
ns-1858.awsdns-40.co.uk, ns-444.awsdns-55.com, ns-754.awsdns-30.net, ns-1213.awsdns-23.org
Mail servers
us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com
DMARC
Reject
SPF
Soft

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from zendesk.com 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

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 zendesk.com.

RuleValueResult
ip4103.151.192.0/23Allowed
ip4104.43.243.237Allowed
ip4149.97.173.180Allowed
ip4163.116.128.0/17Allowed
ip4170.10.128.0/24Allowed
ip4170.10.129.0/24Allowed
ip4170.10.132.56/29Allowed
ip4170.10.132.64/29Allowed
ip4170.10.133.0/24Allowed
ip418.194.95.56Allowed
ip418.198.96.88Allowed
include_spf1.zendesk.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 ip4:103.151.192.0/23 ip4:104.43.243.237 ip4:149.97.173.180 ip4:163.116.128.0/17 ip4:170.10.128.0/24 ip4:170.10.129.0/24 ip4:170.10.132.56/29 ip4:170.10.132.64/29 ip4:170.10.133.0/24 ip4:18.194.95.56 ip4:18.198.96.88 include:_spf1.zendesk.com ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
k1MailchimpRSA 1024 bits · shortActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
mandrillMandrillRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 2048 bitsActive

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

zendesk.com  MX  10 mx1.zendesk.com.
zendesk.com  MX  20 mx2.zendesk.com.

What the record contains

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

zendesk.com  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.zendesk.com, 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.zendesk.com  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.zendesk.com, 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.zendesk.com  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 zendesk.com

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
A216.198.54.2
A216.198.53.2

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
ns-1858.awsdns-40.co.uk205.251.199.66
ns-444.awsdns-55.com205.251.193.188
ns-754.awsdns-30.net205.251.194.242
ns-1213.awsdns-23.org205.251.196.189

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @zendesk.com 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
0us-smtp-inbound-1.mimecast.com170.10.132.141
0us-smtp-inbound-2.mimecast.com170.10.128.221
110aspmx.l.google.com142.251.168.27
120alt1.aspmx.l.google.com192.178.213.27
120alt2.aspmx.l.google.com172.253.148.27
130aspmx2.googlemail.com192.178.213.27

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.zendesk.com.

NameContent
zendesk.commongodb-site-verification=e30FUzWMBmdMTeKqSkHvbokTve6pZOvw
zendesk.comv=spf1 ip4:103.151.192.0/23 ip4:104.43.243.237 ip4:149.97.173.180 ip4:163.116.128.0/17 ip4:170.10.128.0/24 ip4:170.10.129.0/24 ip4:170.10.132.56/29 ip4:170.10.132.64/29 ip4:170.10.133.0/24 ip4:18.194.95.56 ip4:18.198.96.88 include:_spf1.zendesk.com ~all
zendesk.comneat-pulse-domain-verification-VvrqZ7N=34d3bfcf-c556-4b05-a643-2019e0b08983
zendesk.comcanva-site-verification=U1b9IGcuRrxhapP7GzJMAw
zendesk.comsegment-site-verification=GEXWlzlTT3BdxCVHHD6RoG5BBa6eRlcg
zendesk.comhj-ownership=uF7x7UmKwsPqPAfBVE6Tg
zendesk.comgoogle-site-verification=0B1l6Hmp14vgBWc3Yi9Lkdn98KxqEfm3_IcgKsBrUoc
zendesk.combox-domain-verification=a9056151b8e911fcdba552e791c9b4d8b8cc2f16d1bf5e9eced4abfcf3d32a30
zendesk.comonetrust-domain-verification=8cfd00023e5b4b53836b5be310a416cd
zendesk.comgoogle-site-verification=Xcw5HeCMN0tRTA_wtmvXyrNJhnkOfxqydAJziyZYbs8
zendesk.comopenai-domain-verification=dv-cKgK7AWQErYbWivKlTNsL7qJ
zendesk.comfigma-domain-verification=d38ad4a1c1d6029e954e8d5c827d71106fb9844707ae35040523094f7bf4ce19-1740563203
zendesk.comuber-domain-verification=9901fd2f-d629-4f69-9390-17d58123fd00
zendesk.comadobe-idp-site-verification=fbc17c835736a1814a7f09390192ce1da750205f984fa2e7582277ae8ceb1cb2
zendesk.com942552362-2482447
zendesk.comENJUTYRYQ
zendesk.comhubspot-developer-verification=NmFlNmZmNWEtYWFkMS00NjFhLWIzNDEtMGE1ZTMxZDNkY2Y2
zendesk.commailru-verification: c287c4d52bb5fd3c
zendesk.comatlassian-sending-domain-verification=740db120-4e15-4d5d-a7b0-66da110fa222
zendesk.comadobe-idp-site-verification=f87b90e3b016c68095df9b01c1339e70eaeb158b9517711d3c483357c52e2e9d
zendesk.comatlassian-domain-verification=VKatnNN6Z5k9QFIABnW7CaZM1H0z5bp40v0DPNj7ba9zcn8JmG3POJsGOopCJ62O
zendesk.comcursor-domain-verification-w67ssa=qctFFin6s0w3gtIS0YHW62IRx
zendesk.comgoogle-site-verification=egnMXsUGOEcJHf0AEe6sA2ui1hxV56dVP5ekk029C8M
zendesk.combettercomp-verify=eeb8764cb09d9e7ef96ba262012aac38cb571dbbb4fc996b5e3403a665bfe878
zendesk.commiro-verification=3673a7d2bed1d9d95363960b5842c237312cf42a
zendesk.com92cfb88d-b895-4f46-934b-4ecd107e59a1
zendesk.comthousandeyes:p6xh4ric6juof7rvskyh89vk8wvoruq7
zendesk.comca3-f35d69855c2041b4b2d4e861cb9fdd6f
zendesk.comjamf-site-verification=03ryvTnFRg7t7K1fdvusNQ
zendesk.comgoogle-site-verification=LYyGUy8j5JeOt_Faduw1TMPTAR4fEzxfXDoT5B79giw
zendesk.comqxxIl-wTDURBUBT4magGxQ
zendesk.comatlassian-domain-verification=1EBT0aNzHvpjA0mUqdCF+qU/gsS8qxjjo50wYVc4nlCooKAJZUmVI2MnseANx2dd
zendesk.comjTHbayHetmTY@@lm5PYDcPqV*F$W3Z&4AM$6u3acBLo$%xKnt!Kwr^@TP^jB43*pO^F6O8S8RizT8D03gHs#MWhF45fW3Tk%$mI
zendesk.comsmartsheet-site-validation=uO9zE6IM1MDanLjT5EieLufj1cgQCau-
zendesk.com0ed1fe018a2374893f27154f25a6f54784f96b4b3b
zendesk.commongodb-site-verification=yDpxj8ExSlalPAMCJ8OgGqccAE3RKtjy
zendesk.comhubspot-developer-verification=YmRjZTlhZTItZmRhNy00ZjZhLWFhZTYtMDVlNzIwMmM2ZDgx
zendesk.comasv=63067a6ba7ee681dbe3e26dce01a13a5
zendesk.comMS=ms91445911
zendesk.comapple-domain-verification=3pfH4AKY0NA72nHl
zendesk.comcount-okta-7SkGZInGQ7j0z4Cy4efxK
zendesk.comelevenlabs=oJCDeDsCsFVX_0uhh-t_yxJNbDETvr6cnP-UzNYvsr0
zendesk.comMS=ms87052054
zendesk.comdocusign=76412763-2e7d-4385-a9cf-227e938144d6
zendesk.comDirectFedAuthUrl=https://zendesk.okta.com/app/zendesk_aiagentsazurezig_1/exk12ddadohvIJh7H2p8/sso/saml
zendesk.comdocker-verification=c5555047-3106-4749-98b2-1ae5745ba193
_dmarc.zendesk.comv=DMARC1; p=reject
k1._domainkey.zendesk.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
k2._domainkey.zendesk.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.zendesk.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
mandrill._domainkey.zendesk.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB
s1._domainkey.zendesk.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsVvDHm3t4fLLEuXOFfWhT1NmgvKgCTNPG6d63AXHmLCxfnaabDqYvgJ64wy3ndAKXgKIUHQIVqbYBbTS+qRKvujewZ80KZb0aKAF8689NKgkZb7VHwP7IWhrVsy5CjbP/qJdp21XlHAZsWEWDQA5ea8W6/gEGcKIa1fe4iLOObYrBJQLbFgwNSsJjQfGAba2gG3lyrs85IcG6Pcl4IkBxgKihhBDi/9befyGn9co/8Lok8980Pbv1sScbKFMr4vb+Os2Fjy7vqGj3MIONe/I1t9HqYsfz6Lm/PKv5rbc3/K5HmYyrH0/pE88oB6UUGuwvFO3NseG7CSuOSXRq6HqmQIDAQAB
s2._domainkey.zendesk.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1FYEJXSQ4VRCwN6MbOX2s0BethCLd/AOpvarAPc2QdMeKyl7ql5yWgCfP9kqXgpfVj5QthtwDLu8MQGYlOsZ6nTk1Yb0f9oclG7ixznCyv3/w7Ok7Kb4X9sW+xLkRuqCAqNxSp7oWxfKS7AYT5+d224Xv/0dGGhGaCAGqiJUE/QIDAQAB
zendesk1._domainkey.zendesk.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.zendesk.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

IPv4 addresses used by zendesk.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
216.198.54.2Website216.198.54.0/24
216.198.53.2Website216.198.53.0/24
205.251.199.66Name server ns-1858.awsdns-40.co.uk205.251.199.0/24
205.251.193.188Name server ns-444.awsdns-55.com205.251.193.0/24
205.251.194.242Name server ns-754.awsdns-30.net205.251.194.0/24
205.251.196.189Name server ns-1213.awsdns-23.org205.251.196.0/24
170.10.132.141Mail server us-smtp-inbound-1.mimecast.com170.10.132.0/24
170.10.128.221Mail server us-smtp-inbound-2.mimecast.com170.10.128.0/24
142.251.168.27Mail server aspmx.l.google.com142.251.168.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com, Mail server aspmx2.googlemail.com192.178.213.0/24
172.253.148.27Mail server alt2.aspmx.l.google.com172.253.148.0/24
104.43.243.237Authorized by SPF104.43.243.0/24
149.97.173.180Authorized by SPF149.97.173.0/24
18.194.95.56Authorized by SPF18.194.95.0/24
18.198.96.88Authorized by SPF18.198.96.0/24

WHOIS of the domain zendesk.com

Domain Name: ZENDESK.COM
   Registry Domain ID: 157863981_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2024-04-15T11:13:10Z
   Creation Date: 2005-05-16T18:05:12Z
   Registry Expiry Date: 2027-05-16T18:05:12Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: NS-1213.AWSDNS-23.ORG
   Name Server: NS-1858.AWSDNS-40.CO.UK
   Name Server: NS-444.AWSDNS-55.COM
   Name Server: NS-754.AWSDNS-30.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T14:49:58Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.