Summary
- Registrar
- RegistrarSafe, LLC
- Status
- clientDeleteProhibited
- Created on
- January 21, 1991
- Expires on
- January 22, 2034
- Name servers
- c.ns.facebook.com, d.ns.facebook.com, b.ns.facebook.com, a.ns.facebook.com
- Mail servers
- mxb-00082601.gslb.pphosted.com, mxa-00082601.gslb.pphosted.com, mx0b-00082601.pphosted.com, mx0a-00082601.pphosted.com
- DMARC
- Reject
- SPF
- Delegated
- 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 meta.com 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
- —
Record
v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]
Authorized senders (SPF)
The policy is defined by the domain _spf.fb.com (redirect).
SPF lists the servers allowed to send e-mails for meta.com.
| Rule | Value | Result |
|---|---|---|
| redirect | _spf.fb.com | — |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 redirect=_spf.fb.com
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 meta.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from meta.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 @meta.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
meta.com MX 10 mx1.meta.com. meta.com MX 20 mx2.meta.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.meta.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
meta.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.meta.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.meta.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.meta.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.meta.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 meta.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.
| Type | IP address |
|---|---|
| A | 157.240.196.17 |
| AAAA | 2a03:2880:f042:112:face:b00c:0: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.
| Server | IP address |
|---|---|
| c.ns.facebook.com | 185.89.218.12 |
| d.ns.facebook.com | 185.89.219.12 |
| b.ns.facebook.com | 129.134.31.12 |
| a.ns.facebook.com | 129.134.30.12 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @meta.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.
| Priority | Server | IP address |
|---|---|---|
| 10 | mxb-00082601.gslb.pphosted.com | 67.231.153.30 |
| 10 | mxa-00082601.gslb.pphosted.com | 67.231.153.30 |
| 20 | mx0b-00082601.pphosted.com | 67.231.153.30 |
| 20 | mx0a-00082601.pphosted.com | 67.231.145.42 |
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.meta.com.
| Name | Content |
|---|---|
| meta.com | krisp-domain-verification=Qo1RXvowjIIJwtkuCGLXn9rb42ouFiD1 |
| meta.com | 2678481 |
| meta.com | SFMC-QntGqBQWJQgWAmziYTSMLC_RFK-QY0XoDqCb59qo |
| meta.com | mentimeter-8599dcd1-e0da-4326-882e-7570e7c942fb |
| meta.com | openai-domain-verification=dv-aYIcEKTatV2YiUmh0KxVxHYt |
| meta.com | smartsheet-site-validation=czIYUcozQp6VyDu8DMpnjSGZAulejP36 |
| meta.com | e1602cc4-c094-4810-9ba1-487b9c171d0a |
| meta.com | amazon-business-verification=38d8ff3ff8bcc0a9521fbcbc3fbeaaf62b40e76dc5fe28602707a1caa75e093c |
| meta.com | wiz-domain-verification=49c8babe4e9832f92b48be99a2ff9f20e464f9fe03e12e1d25f961315688e1b0 |
| meta.com | liveramp-site-verification=7o_qYDez8Z-ZP1F8NGIxt7dgcBUOU4njB0_iDvl2_GM |
| meta.com | airtable-verification=b2eb6311898506343df24da9c49c8f39 |
| meta.com | perplexity-ai-domain-verification-jzzrvg=KghiEJzer9K0EUTqUvCJfM4FI |
| meta.com | anthropic-domain-verification-vb762t=ezl2XXGyq8tXMTx0oArON1hm7 |
| meta.com | stripe-verification=3556f4515d122d1dfc498139862bb8759fc73dc9172ce8e75ccacfb31886424a |
| meta.com | zoom-domain-verification=4b2ef4e1-6dee-4483-9869-9bef353fd147 |
| meta.com | censys-domain-verification=Yo-juPBT_qmJ-qe2cmh9ytUXJhAPx0fy3l8UfLW6iFkG |
| meta.com | gamma-domain-verification-zgq5h4=OgSeTkAEhYH7u8jgIcEws1F3b |
| meta.com | airtable-verification=81b6197107c896de62ab91cf767f94a8 |
| meta.com | apple-domain-verification=jVVbKL4kbd6qwW9I3HaF82Pvx4Dw_ZLoP4fCfLN9VtA |
| meta.com | slack-domain-verification=0BD3JdNG4KXfQalAcVxN5d3VHeHLe0nYNYAYcxm9 |
| meta.com | airtable-verification=e5ea432248c225409579034427e268a9 |
| meta.com | atlassian-domain-verification=CvZmRJmM9sx250sAzSzZ6pVinoosIPNmnhGqfKcnYi5mVuYyaWzVUNMk6x69g770 |
| meta.com | bluebeam-verification=ndxhnuqs84dkpsrlyj8v8hwikmaudw |
| meta.com | cursor-domain-verification-cd09k5=Ptq7dEvh3q5u7jQpZgfJdov8D |
| meta.com | canva-site-verification=iQtpnfmzYgLxP8uf_0fN3A |
| meta.com | v=spf1 redirect=_spf.fb.com |
| meta.com | manus-domain-verification-ccwyr4=xqSOkWFnTHeCFASkoQ5YW3VhF |
| meta.com | d9895a85-87c3-4c89-a47f-f62da6172abf |
| meta.com | SFMC--IBmbMl8WsU-Dj1SIZj7RCsKChznFkO3raDqol6l |
| meta.com | rzp-site-verification=224114166287f72512718dbdf148433b |
| meta.com | mentimeter-16bdc82d-93be-47de-a6d4-fd6adb17c403 |
| meta.com | elevenlabs=JM_cDh_L6SUGrL_3im6KtdDonBDsX9jiv5f_BarPOC8 |
| meta.com | MS=ms62716295 |
| meta.com | lucidchart-verification=YWykPZR9OAfOMLreWjllpom6N |
| meta.com | openai-domain-verification=dv-9VWR0XUv3Tg6cTv9njNqbwN8 |
| meta.com | meshy-verification=019ba48cb37a7d60ae664246433708b0 |
| meta.com | parkable-domain-verification=BEBNZLmadNNXu5J3gl7zZcRytRbvwTlmAFAtQuGel4E= |
| meta.com | google-site-verification=HR4Xo3vzMUlBppYoVbkYJ9cTG2rHaFYsCDyy8w1Tlqk |
| meta.com | linear-domain-verification=sxhfmp46dir3 |
| meta.com | masv=sLRNYzsZOaYnCZDQulTexcyzRkYNUJlF |
| meta.com | flexera-domain-verification-vcvotrexfxpeibla |
| meta.com | atlassian-domain-verification=I7HLjLnlhJiDT58wzrru2Pd/2cRWa3AKlgCjDPOO43GMP7H0QuafH6eBts3D1GaP |
| meta.com | dust-domain-verification-98xyt7=10CFebRuinJsIZ3GBaR3odOk |
| meta.com | stripe-verification=739B2DF1319B373225C1D41F1C5FB9EB45CB3EB33ED798FCDF3AEAEAC12C9CBC |
| meta.com | airtable-verification=16d7d6b6aea82b1831e664e377bf20cb |
| meta.com | hubspot-developer-verification=MTkyYjRkNmYtODk4Ny00NmVjLWE1MWUtMzZjZTMxNWQ2ZmEx |
| meta.com | 88d92136-5f42-4012-ae48-d6eb2b55db10 |
| meta.com | mixpanel-domain-verify=9cfd2929-c7bb-4d49-a81a-419bf4c14ebe |
| meta.com | smartsheet-site-validation=UxvM1DM07tqKMCws2PpHGqCRqbnvX_sS |
| meta.com | bitrise-verification=abf0a61c07a7d976-rH78UI9wM4ed |
| meta.com | bWV0YQ== |
| meta.com | rep-data-domain-verification-vgh5br=f7JlbZ6f7uQjaVUVsrkIL0dZm |
| meta.com | R0METvdRK3nQWdKcRgc6tUud-lJefoVG |
| meta.com | flexera-domain-verification-kaxmydsxzfbicdfr |
| meta.com | google-site-verification=mCIIkbiX5oDurbChBmsJFS9T8Qm7a7WldZkrq57X-eE |
| meta.com | intercom-domain-validation=dc8938df-ba79-4019-8809-1b836c9117c4 |
| meta.com | shopify-verification-code=JUzxnVutn7DU5rUiF8j0Q9mlCOdU2h |
| _dmarc.meta.com | v=DMARC1; p=reject; pct=100; rua=mailto:[email protected] |
Related IP addresses
IPv4 addresses used by meta.com: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 157.240.196.17 | Website | 157.240.196.0/24 |
| 185.89.218.12 | Name server c.ns.facebook.com | 185.89.218.0/24 |
| 185.89.219.12 | Name server d.ns.facebook.com | 185.89.219.0/24 |
| 129.134.31.12 | Name server b.ns.facebook.com | 129.134.31.0/24 |
| 129.134.30.12 | Name server a.ns.facebook.com | 129.134.30.0/24 |
| 67.231.153.30 | Mail server mxb-00082601.gslb.pphosted.com, Mail server mxa-00082601.gslb.pphosted.com, Mail server mx0b-00082601.pphosted.com | 67.231.153.0/24 |
| 67.231.145.42 | Mail server mx0a-00082601.pphosted.com | 67.231.145.0/24 |
WHOIS of the domain meta.com
Domain Name: META.COM Registry Domain ID: 1433704_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.registrarsafe.com Registrar URL: http://www.registrarsafe.com Updated Date: 2025-01-22T16:09:14Z Creation Date: 1991-01-21T05:00:00Z Registry Expiry Date: 2034-01-22T05:00:00Z Registrar: RegistrarSafe, LLC Registrar IANA ID: 3237 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1-650-308-7004 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: A.NS.FACEBOOK.COM Name Server: B.NS.FACEBOOK.COM Name Server: C.NS.FACEBOOK.COM Name Server: D.NS.FACEBOOK.COM DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of whois database: 2026-10-02T07:37: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.