The Role of Domain-Level Verification Checks: A Complete Guide with Case Study
1. Introduction
Email marketing has become an important communication tool for businesses, organizations, and individuals. Companies use email campaigns to promote products, share information, communicate with customers, and build long-term relationships. However, sending emails to invalid or poorly configured addresses can create serious problems for email deliverability.
One important method of improving email deliverability is domain-level verification. Domain-level verification checks help determine whether an email domain is valid, active, properly configured, and capable of receiving emails.
An email address consists of two main parts: the username and the domain name. For example, in [email protected], “customer” is the username, while “example.com” is the domain.
Although an email address may look correct, its domain might not exist, might have expired, or might not have the necessary mail server records. This is why checking only the email address format is not enough.
Domain-level verification helps businesses identify potential delivery problems before sending large email campaigns. It reduces unnecessary sending attempts, improves list quality, protects sender reputation, and supports better communication.
This article explains the meaning of domain-level verification, how it works, its importance, common checks, challenges, best practices, and a practical case study.
2. What Is Domain-Level Verification?
Domain-level verification is the process of checking whether the domain part of an email address is valid and properly configured to receive email messages.
For example, consider these email addresses:
During domain-level verification, the verification system checks the domains rather than focusing only on the individual usernames.
It investigates whether the domain exists, whether its DNS records are available, and whether it has mail servers configured to handle incoming messages.
Domain-level verification is an important part of email verification because an email address cannot receive messages if its domain is invalid or lacks an appropriate mail-handling configuration.
However, a valid domain does not automatically mean that every email address under that domain exists. Domain-level checks must therefore be combined with other verification methods.
3. How Domain-Level Verification Works
Domain-level verification involves several technical checks that help determine whether an email domain is properly configured.
The process generally includes the following steps.
A. Domain Syntax Checking
The first step is checking whether the domain follows the correct naming structure.
For example:
-
example.com – Valid format.
-
company.org – Valid format.
-
example..com – Invalid format.
-
[email protected] – Invalid domain structure.
Syntax checking identifies incorrectly written domains before more advanced verification begins.
B. DNS Record Checking
DNS stands for Domain Name System. It translates domain names into information that computers and servers can understand.
A verification system checks DNS records to determine whether the domain exists and has relevant configurations.
Important DNS records include:
-
A Record: Connects a domain to an IPv4 address.
-
AAAA Record: Connects a domain to an IPv6 address.
-
MX Record: Identifies mail servers responsible for receiving emails.
-
TXT Record: Stores information used for domain verification and email authentication.
These records help verification systems understand how a domain operates.
C. MX Record Verification
MX stands for Mail Exchange.
MX records identify the mail servers responsible for receiving emails sent to a particular domain.
For example, when someone sends an email to [email protected], the sending server checks the MX records for example.com to determine where the message should be delivered.
If a domain has valid MX records, it usually indicates that it has a configured email receiving service.
However, having MX records does not guarantee that every mailbox on the domain exists.
D. Mail Server Identification
After finding the MX records, the verification system identifies the mail servers associated with the domain.
It checks whether the listed mail servers can be resolved through DNS and whether they appear to be configured to handle email.
This helps identify domains with missing, incorrect, or unreachable mail server configurations.
E. DNS Configuration Analysis
Some verification systems also examine additional DNS settings to understand the domain’s email configuration.
These may include:
-
SPF records.
-
DKIM records.
-
DMARC records.
These records help protect email communication against spoofing and unauthorized sending.
It is important to understand that SPF, DKIM, and DMARC mainly support email authentication. Their presence does not independently prove that a domain can receive emails.
4. Importance of Domain-Level Verification Checks
Domain-level verification provides several benefits to businesses that depend on email communication.
A. Improves Email Deliverability
One major benefit is improved email deliverability.
When businesses send emails to domains that do not exist or cannot receive messages, those emails may bounce.
Repeated delivery failures can negatively affect sending reputation.
Domain-level checks help identify problematic domains before campaigns are launched.
B. Reduces Email Bounce Rates
A bounce occurs when an email cannot be delivered to its intended destination.
Some common causes include:
-
Non-existent domains.
-
Missing MX records.
-
Incorrect DNS configurations.
-
Unavailable mail servers.
By identifying these problems early, businesses can reduce avoidable delivery failures.
C. Protects Sender Reputation
Email service providers monitor sending behaviour to identify suspicious or unwanted email activity.
A high number of failed deliveries may indicate poor list quality.
Domain-level verification helps businesses maintain cleaner mailing lists and avoid sending messages to obviously invalid domains.
D. Saves Time and Money
Sending emails to invalid domains wastes resources.
Businesses may spend money on email marketing platforms, campaign management, and verification services.
Checking domains before sending campaigns helps reduce unnecessary sending attempts and improves the efficiency of marketing activities.
E. Supports Better Email List Management
Email lists naturally become outdated over time.
Businesses may collect incorrect domains, experience domain changes, or retain old addresses belonging to inactive organizations.
Regular domain-level verification helps identify these problems and supports better database maintenance.
F. Improves Campaign Performance
When businesses maintain cleaner email lists, they can make better use of their marketing resources.
Although domain verification does not guarantee higher open rates or conversions, it helps create a stronger foundation for successful email campaigns.
5. Common Domain-Level Verification Results
Email verification systems usually classify domain checks into different results.
Understanding these results helps businesses decide what action to take.
| Verification result | Meaning | Recommended action |
|---|---|---|
| Valid domain | Domain exists and has suitable email configuration | Continue verification |
| Invalid domain | Domain does not exist or is incorrectly configured | Remove or correct |
| No MX record | No mail exchange record was found | Investigate further |
| DNS error | DNS information could not be retrieved | Retry later |
| Disposable domain | Domain provides temporary email services | Apply campaign policy |
| Catch-all domain | Domain may accept emails sent to different addresses | Mark for additional checks |
These results should not be treated as absolute guarantees. DNS problems may be temporary, and some mail servers use unusual configurations.
6. Challenges Associated with Domain-Level Verification
Although domain-level verification is useful, it has certain limitations.
A. Temporary DNS Problems
Sometimes DNS servers become unavailable or respond slowly.
This may cause verification systems to report errors even when the domain is legitimate.
Businesses should avoid immediately deleting every domain that produces a temporary DNS error.
B. Catch-All Domains
Some organizations configure their mail servers to accept emails sent to almost any address under their domain.
These are known as catch-all domains.
For example, a catch-all server might accept messages sent to:
This makes it difficult to determine whether a particular mailbox exists.
C. Changing Domain Configurations
Organizations sometimes change their hosting providers, email services, or DNS configurations.
During these changes, email verification results may temporarily become inaccurate.
D. False Positives and False Negatives
A verification tool may incorrectly classify a domain because of temporary network issues or unusual server settings.
For this reason, domain-level verification should be combined with other checks instead of being treated as the only verification method.
E. Limited Information About Individual Mailboxes
One of the biggest limitations is that domain-level verification cannot always confirm whether an individual email account exists.
A valid domain with working MX records may still contain invalid or inactive email addresses.
7. Best Practices for Domain-Level Verification
Businesses should follow certain practices to get better results from domain-level verification.
1. Verify domains before sending campaigns.
Check domains before uploading or using large email lists.
2. Combine domain checks with syntax verification.
Make sure email addresses follow the correct structure before checking their domains.
3. Check MX records regularly.
Confirm that domains have appropriate mail exchange configurations.
4. Use reliable verification tools.
Choose verification services that provide detailed results and support DNS-based checks.
5. Recheck temporary errors.
Do not immediately remove domains that experience temporary DNS failures.
6. Monitor email bounce rates.
Review campaign reports to identify repeated delivery problems.
7. Maintain updated email lists.
Remove confirmed invalid domains and correct outdated information.
8. Follow email marketing regulations.
Only send campaigns to people whose addresses were collected and used in accordance with applicable privacy and marketing laws.
8. Case Study: How a Digital Marketing Company Improved Email Deliverability Through Domain-Level Verification
Background
A digital marketing company called BrightWave Marketing managed email campaigns for several small and medium-sized businesses.
The company maintained an email database containing approximately 50,000 contacts collected through website registrations, customer enquiries, newsletters, and previous marketing campaigns.
Initially, the company focused mainly on checking whether email addresses followed the correct format.
However, it did not regularly examine the domains associated with those addresses.
As a result, some email campaigns experienced high bounce rates and delivery problems.
The Problem
After sending several campaigns, BrightWave Marketing noticed that many emails were not reaching their intended recipients.
An investigation revealed several problems:
-
Some email addresses contained non-existent domains.
-
Several domains had no valid MX records.
-
Some company domains had outdated DNS configurations.
-
Some contacts used temporary email services.
-
Certain domains experienced temporary DNS resolution failures.
The company realized that checking email formats alone was insufficient.
It needed a more complete verification process that included domain-level checks.
The Solution
BrightWave Marketing introduced a domain-level verification process before sending future campaigns.
The process involved five major activities.
Step 1: Collecting the email database
The company exported its 50,000 email addresses into a verification system.
Step 2: Checking domain syntax
The system identified incorrectly formatted domains and separated them for correction.
Step 3: Checking DNS records
The company examined the DNS configuration of each domain to determine whether it existed and could be resolved.
Step 4: Checking MX records
The verification system identified domains with valid mail exchange records and separated those with missing or incorrect configurations.
Step 5: Organizing verification results
The company divided its email database into different groups:
-
Valid domains.
-
Invalid domains.
-
Domains without MX records.
-
Temporary DNS errors.
-
Catch-all domains.
-
Disposable email domains.
The marketing team reviewed the results before approving the email list for campaigns.
Results
After introducing domain-level verification, BrightWave Marketing noticed improvements in its email list management.
The company removed confirmed invalid domains, corrected incorrectly entered domains, and investigated temporary verification failures.
It also reduced unnecessary sending attempts to domains that were not properly configured to receive emails.
The marketing team became more confident when preparing large campaigns because it had better information about the quality of its contact database.
The company also established a regular verification schedule to prevent outdated domain information from affecting future campaigns.
Lessons Learned
The case study demonstrated several important lessons:
-
Checking email format alone is not enough.
-
DNS and MX record checks help identify domain-related delivery problems.
-
Temporary DNS errors should be investigated before removing contacts.
-
Catch-all domains require additional verification.
-
Regular verification helps maintain email database quality.
-
Domain-level checks should be combined with mailbox-level verification.
The experience showed that domain-level verification is an important part of maintaining a healthy email marketing system.
Note: BrightWave Marketing is a fictional company, and the case study illustrates a practical example rather than reporting measured results from a real organization.
9. The Future of Domain-Level Verification
Domain-level verification is expected to remain important as email communication continues to grow.
Modern verification systems are becoming more advanced by combining DNS analysis, automated monitoring, server response checks, and intelligent classification.
Artificial intelligence may also help identify unusual domain patterns and detect potential email delivery problems.
In the future, businesses may benefit from more automated systems that regularly monitor domain configurations and alert administrators when problems occur.
These improvements can help organizations maintain cleaner email databases and improve the reliability of their email communication.
However, even advanced verification systems will need to account for temporary DNS problems, privacy protections, and differences in how email servers are configured.
The History of Domain-Level Verification Checks
1. Introduction
Domain-level verification checks have played an important role in the development of email communication, internet security, and email marketing. As businesses increasingly depend on email to communicate with customers, the need to ensure that email domains are valid, properly configured, and trustworthy has become more important.
In the early days of electronic communication, email systems were relatively simple. Users could send messages across connected computers without the advanced security checks used today. As the internet expanded, however, email became a major communication platform for businesses, individuals, educational institutions, and government organizations.
This growth also introduced several problems, including spam, fake email addresses, phishing attacks, invalid domains, and unsuccessful email deliveries. These challenges encouraged the development of different verification methods to improve the reliability of email communication.
Domain-level verification gradually became an important part of this development. It allowed email systems to examine the domain portion of an email address and determine whether it existed and had appropriate email-related configurations.
For example, in the email address [email protected], the domain is example.com. Domain-level checks can investigate whether this domain exists, whether it has valid DNS information, and whether it has mail exchange records.
The history of domain-level verification is closely connected to the development of the Domain Name System (DNS), Simple Mail Transfer Protocol (SMTP), Mail Exchange (MX) records, Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC).
Understanding this history helps explain how modern email verification systems developed and why domain-level checks remain important today.
2. The Early History of Email Communication
Email communication began in the early development of computer networks. During this period, email was mainly used by researchers, universities, and organizations connected through private or limited computer networks.
One important milestone occurred in 1971 when Ray Tomlinson introduced network email and helped establish the use of the @ symbol to separate a user’s name from the destination computer or host.
At that time, email systems were not designed to handle the enormous number of users and security threats that exist today.
Most users communicated within relatively small and trusted networks. There was little need for advanced domain verification because the number of connected systems was limited.
As computer networks expanded, email became more widely available. People began using it for personal communication, business transactions, and information sharing.
However, the increasing number of users created new challenges. Email systems needed better ways to identify destinations, locate receiving servers, and manage messages across different networks.
These developments created the foundation for modern domain-level verification.
3. The Development of DNS in the 1980s
One of the most important developments in the history of domain-level verification was the introduction of the Domain Name System.
Before DNS became widely established, computers on networks depended heavily on manually maintained host information to identify other computers.
As the internet grew, maintaining these records became increasingly difficult.
In 1983, Paul Mockapetris introduced the DNS architecture through RFC 882 and RFC 883. These documents established the foundation for a distributed system that could translate human-readable domain names into information needed by network computers.
DNS made it easier to identify internet resources without requiring users to remember numerical IP addresses.
For example, instead of remembering a server’s IP address, users could access a service through a domain name.
DNS later became essential to email verification because it provided a way to publish information about domains and their mail servers.
This development made it possible for email systems to check whether a domain existed and identify the servers responsible for receiving its messages.
4. The Introduction of SMTP and MX Records
Another major development occurred with the standardization of Simple Mail Transfer Protocol (SMTP).
SMTP became the foundation for transferring email messages between servers. Its early specification was published as RFC 821 in 1982.
As email communication expanded, systems needed a reliable method for identifying the correct receiving mail server for each domain.
This led to the development of Mail Exchange records, commonly known as MX records.
MX records became an important part of DNS-based email routing. They identify the mail servers responsible for receiving messages for a particular domain.
For example, when someone sends an email to [email protected], the sending mail server checks the DNS records for company.com to determine which mail server should receive the message.
This development created an important foundation for domain-level verification.
Instead of checking only whether an email address looked correct, systems could investigate whether its domain had the necessary mail-handling configuration.
MX records therefore became one of the most important checks used by modern email verification services.
5. The Growth of the Internet and the Rise of Email Problems in the 1990s
During the 1990s, internet access expanded rapidly. More businesses, educational institutions, and individuals began using email as an everyday communication tool.
Companies started using email to communicate with customers, advertise products, send invoices, and share important business information.
However, the rapid growth of email also introduced serious problems.
Some users began sending unsolicited bulk messages, commonly known as spam. Others used fake email addresses and misleading domain names to deceive recipients.
Businesses also experienced problems with invalid domains and unsuccessful email deliveries.
For example, a company might collect thousands of email addresses through an online registration form. Some addresses could contain spelling mistakes, while others might use domains that no longer existed.
Sending messages to these addresses resulted in unnecessary delivery failures.
These challenges increased the demand for better email verification systems.
Domain-level checks became particularly useful because they allowed organizations to identify problems with domains before attempting to send large numbers of messages.
During this period, DNS lookups and MX record checks became important technical methods for investigating email domains.
Although these checks could not confirm that every individual mailbox existed, they helped identify domains that were unable to receive email.
6. The Development of Advanced Email Verification in the 2000s
The early 2000s marked an important period in the development of email security and verification.
As email became a major business communication channel, spam and fraudulent messages continued increasing.
Traditional domain checks were useful, but they could not solve every email security problem.
For example, a spammer could send a message using a fake sender address while using an actual, functioning mail server.
This meant that verifying whether a domain existed was not enough. Email systems also needed ways to determine whether a sender was authorized to use a particular domain.
Several technologies were developed to address this problem.
A. Development of Sender Policy Framework (SPF)
Sender Policy Framework, commonly known as SPF, emerged in the early 2000s.
SPF allowed domain owners to publish DNS information identifying which mail servers were authorized to send emails on behalf of their domains.
This was an important development because receiving mail servers could check whether a message came from an authorized sending server.
SPF was formally documented in RFC 4408 in 2006 and later updated through RFC 7208 in 2014.
It strengthened domain-level email authentication by allowing organizations to publish their approved sending sources through DNS.
For example, a company could configure its domain to authorize its business email provider to send messages on its behalf.
If another server attempted to send messages using that domain without authorization, receiving systems could detect the problem through SPF checks.
B. Development of DomainKeys Identified Mail (DKIM)
Another important development was DomainKeys Identified Mail, known as DKIM.
DKIM introduced cryptographic signatures that allowed receiving mail servers to verify whether a message had been signed by an authorized domain.
The technology developed from earlier approaches, including Yahoo’s DomainKeys and Cisco’s Identified Internet Mail.
DKIM was standardized in RFC 4871 in 2007 and later updated through RFC 6376 in 2011.
Unlike ordinary domain existence checks, DKIM helped verify the authenticity and integrity of email messages.
It used public and private cryptographic keys, with the public key published through DNS.
This allowed receiving servers to check the signature attached to an email message.
SPF and DKIM represented major improvements in the development of domain-level email security.
7. The Introduction of DMARC in 2012
One of the most significant developments in domain-level email authentication was the introduction of Domain-based Message Authentication, Reporting, and Conformance (DMARC).
DMARC was developed to bring existing email authentication methods together and provide domain owners with greater control over how receiving servers handled unauthenticated messages.
The specification was published in January 2012 and later documented as RFC 7489 in March 2015.
DMARC works with SPF and DKIM to determine whether email messages are properly authenticated and aligned with the domain shown in the visible sender address.
It also allows domain owners to publish policies describing how receiving systems should handle messages that fail authentication.
These policies include:
-
None: Monitor email authentication results without requesting special handling.
-
Quarantine: Ask receiving systems to treat failing messages as suspicious.
-
Reject: Ask receiving systems to reject messages that fail the applicable DMARC policy.
DMARC also provides reporting capabilities that help organizations understand how their domains are being used.
This was a major step forward because businesses could monitor unauthorized email activity and improve their domain security.
According to the National Institute of Standards and Technology (NIST), SPF, DKIM, and DMARC provide complementary methods for email authentication, message integrity, and reporting.
NIST+1
8. The Evolution of Automated Domain Verification Tools
As email marketing became more popular, businesses began managing larger contact databases.
Manually checking every domain became difficult and time-consuming.
This created demand for automated email verification platforms.
These tools made it possible to upload thousands or millions of email addresses and perform different verification checks automatically.
Modern verification platforms introduced several important features:
1. Automatic DNS checking: Systems could examine whether a domain existed and whether its DNS information could be retrieved.
2. MX record identification: Tools could automatically identify the mail servers associated with a domain.
3. Disposable domain detection: Verification systems could identify domains associated with temporary email services.
4. Catch-all detection: Some tools began identifying domains configured to accept messages sent to different addresses.
5. Domain classification: Email addresses could be grouped according to the condition of their domains.
6. Automated reporting: Businesses could receive reports showing valid, invalid, risky, and uncertain verification results.
These developments made email verification faster and more accessible to organizations of different sizes.
Instead of checking addresses individually, businesses could process entire email lists through automated systems.
9. Domain-Level Verification in the 2010s
During the 2010s, domain-level verification became increasingly important because of the growing importance of digital marketing and online business communication.
Companies started using email automation platforms to send newsletters, promotional offers, customer notifications, and transactional messages.
As email databases increased in size, maintaining accurate contact information became a major responsibility.
Domain-level verification helped organizations identify outdated and incorrectly configured domains.
At the same time, email authentication standards continued improving.
DKIM was updated through RFC 6376 in 2011, while SPF was updated through RFC 7208 in 2014.
DMARC was formally documented in 2015.
These developments improved the ability of email systems to authenticate domains and detect unauthorized use.
Businesses also became more aware of sender reputation.
Email service providers increasingly used sending behaviour, authentication results, and recipient engagement signals when evaluating incoming messages.
This encouraged marketers to maintain cleaner email databases and adopt regular verification practices.
Domain-level checks became an important part of responsible email marketing.
10. Modern Developments in Domain-Level Verification
Today, domain-level verification is more advanced than it was during the early development of email communication.
Modern verification systems combine several technologies to investigate domains and identify potential delivery problems.
These systems may perform:
-
Domain syntax validation.
-
DNS record lookups.
-
MX record verification.
-
Mail server identification.
-
Disposable domain detection.
-
Catch-all domain checks.
-
SPF record analysis.
-
DKIM configuration checks.
-
DMARC policy analysis.
Another important development is the increased use of automation and intelligent classification.
Some verification platforms can process large email databases, identify suspicious patterns, and organize results into useful categories.
Internationalized domain names have also received attention. In 2019, RFC 8616 clarified how SPF, DKIM, and DMARC apply to internationalized email environments.
RFC Editor
In 2026, DMARC’s technical standards also continued evolving. RFC 9989, published in May 2026, replaced RFC 7489 as the main DMARC specification.
RFC Editor+1
These developments demonstrate that domain-level email security continues to evolve alongside internet technology.
11. The Role of Domain-Level Verification in Modern Email Marketing
Domain-level verification has become an important part of modern email marketing because businesses depend on accurate email databases to communicate effectively.
In the past, marketers could collect email addresses and immediately add them to mailing lists without performing detailed verification.
Today, businesses understand that sending messages to invalid or incorrectly configured domains can waste resources and contribute to poor delivery performance.
Domain-level verification helps marketers identify problems before launching campaigns.
For example, an organization preparing a newsletter for 20,000 subscribers can check the domains associated with its contact list before sending messages.
If the verification system identifies domains that do not exist or have no suitable mail configuration, the marketing team can investigate them before launching the campaign.
This helps businesses:
-
Reduce unnecessary email delivery failures.
-
Maintain cleaner contact databases.
-
Identify potentially problematic domains.
-
Improve email campaign management.
-
Protect their sending infrastructure.
-
Support better email authentication practices.
However, domain-level verification should always be combined with individual email address verification and responsible sending practices.
12. The Future of Domain-Level Verification Checks
The future of domain-level verification will likely involve more automation, improved security analysis, and intelligent verification systems.
As businesses continue adopting cloud-based email services, verification platforms will need to support increasingly complex domain configurations.
Artificial intelligence and machine learning may also improve the ability of verification systems to recognize unusual domain patterns and identify potential configuration problems.
Another important area of development is real-time domain monitoring.
Rather than checking a domain only when an email list is uploaded, future systems may continuously monitor DNS records and alert businesses when important configurations change.
For example, a company could receive an alert when its MX records become unavailable or when its SPF configuration contains an error.
Such improvements could help organizations identify problems earlier and maintain reliable email communication.
Nevertheless, future verification systems will still need to distinguish between genuine domain problems and temporary technical failures.
13. Conclusion
The history of domain-level verification checks demonstrates how email communication has developed from a simple messaging system into a sophisticated global communication platform.
The introduction of DNS in the 1980s created the foundation for identifying domains and locating internet resources. The development of SMTP and MX records improved email delivery by allowing sending servers to identify receiving mail servers.
During the 1990s and early 2000s, the growth of internet usage, spam, and fraudulent email activities increased the need for more advanced verification methods.
The introduction of SPF, DKIM, and DMARC further improved domain-level email authentication and security.
Over time, automated verification platforms made it easier for businesses to examine large email databases, identify invalid domains, and maintain better contact information.
Today, domain-level verification remains an important part of email marketing, email security, and business communication.
Its development shows that maintaining reliable email communication requires more than checking whether an address is correctly written. Businesses must also understand the domains behind those addresses and ensure that their email configurations are appropriate.
As technology continues to advance, domain-level verification will remain an important tool for improving email reliability, protecting domain reputation, and supporting effective digital communication.
14. Historical References
The following technical documents and publications provide background information on the development of domain-level verification and email authentication:
-
RFC 821 (1982): Simple Mail Transfer Protocol (SMTP).
-
RFC 882 and RFC 883 (1983): Early Domain Name System specifications.
-
RFC 4408 (2006): Sender Policy Framework (SPF).
-
RFC 4871 (2007): DomainKeys Identified Mail (DKIM).
-
RFC 6376 (2011): Updated DKIM specification.
-
RFC 7208 (2014): Updated SPF specification.
-
RFC 7489 (2015): Domain-based Message Authentication, Reporting, and Conformance (DMARC).
-
NIST Technical Note 1945 (2017): Email Authentication Mechanisms: DMARC, SPF and DKIM.
-
RFC 8616 (2019): Email Authentication for Internationalized Mail.
-
RFC 9989 (2026): Updated DMARC specification.
