Dataweaz

lbl.gov

Summary

Registrar
get.gov
Status
serverTransferProhibited
Created on
October 2, 1997
Expires on
August 28, 2027
Name servers
adns.lbl.gov, adns2.es.net, adns1.es.net
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
SPF
Soft

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from lbl.gov but fails SPF and DKIM checks.

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

Record

v=DMARC1;p=none;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected]

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 lbl.gov.

RuleValueResult
includespfint.lbl.govAllowed
ip62001:400:310::/64Allowed
ip4198.124.252.166Allowed
ip4198.129.252.90Allowed
ip62001:400:210:3::3Allowed
ip62001:400:6440:3::3Allowed
ip62001:400:ffff:ffff:ffff:ffff:ffff:ff25Allowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:spfint.lbl.gov ip6:2001:400:310::/64 ip4:198.124.252.166 ip4:198.129.252.90 ip6:2001:400:210:3::3 ip6:2001:400:6440:3::3 ip6:2001:400:ffff:ffff:ffff:ffff:ffff:ff25 ~all

E-mail signing (DKIM)

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

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

lbl.gov  MX  10 mx1.lbl.gov.
lbl.gov  MX  20 mx2.lbl.gov.

What the record contains

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

lbl.gov  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.lbl.gov, 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.lbl.gov  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.lbl.gov, 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.lbl.gov  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 lbl.gov

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
A131.243.228.58

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
adns.lbl.gov131.243.5.53
adns2.es.net192.188.22.52
adns1.es.net192.188.22.22

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @lbl.gov 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.com142.250.110.27
5alt2.aspmx.l.google.com142.251.127.26
5alt1.aspmx.l.google.com192.178.213.27
10alt4.aspmx.l.google.com142.250.147.27
10alt3.aspmx.l.google.com172.253.148.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.lbl.gov.

NameContent
lbl.govbox-domain-verification=c15c129b49edfeda4f2998f51ab86512161af5251e765e73f8c312e8438981f7
lbl.govatlassian-domain-verification=PZUpopCxEiaiTq0EmOJiF1oCvepxHULA64xstX0NEVv2Yx7HgFpB4P6hKTHyYXre
lbl.govopenai-domain-verification=dv-sfvJakqc0pd21hOhaJqnqUTd
lbl.govgoogle-site-verification=2dpiQJ9xZceLN1pILOitQbB163hcYnJhaK7I3y8BJ-8
lbl.govdocusign=1eee3cad-4748-4aaf-9ed7-b2605c9483cc
lbl.govgoogle-site-verification=vRtEcyl-bcyq9LlAx-IKqgI_Uw5H4I_Fn0bIxGQwWek
lbl.govanthropic-domain-verification-h102fx=00CIodRx8WUfix92z4OI6tLwt
lbl.govv=spf1 include:spfint.lbl.gov ip6:2001:400:310::/64 ip4:198.124.252.166 ip4:198.129.252.90 ip6:2001:400:210:3::3 ip6:2001:400:6440:3::3 ip6:2001:400:ffff:ffff:ffff:ffff:ffff:ff25 ~all
lbl.govdocusign=0f6bb425-7a31-4e68-82be-fbd457f31774
lbl.govlogmein-verification-code=b89f15f9-74de-42e6-beba-fc61fb213ff5
lbl.govgoogle-site-verification=GhY8O8foCyslsuOSh5VOpyIt6kp9gaZF_6X2WbtVQVI
lbl.govcanva-site-verification=mgUHPJc6r0NE6Q4prE9zpQ
lbl.govc3c383f2-a153-4617-9717-54e564cb59e0
lbl.govatlassian-domain-verification=9IP0nkgLSi6HnSykGR9L6B4/iYnroZIv6KiAGQZfcNV5YAZOLabe65zayxGnVyp0
lbl.govqa1mnrllgnbfii00rdk66vjvm2
lbl.govca3-7d1dfaea22424670b66fd99306419327
lbl.govpardot1008322=a85fde4e241411eab5a95741a5485759066251b9421d2aa2a4fbf634872dbed4
_dmarc.lbl.govv=DMARC1;p=none;rua=mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected]
google._domainkey.lbl.govv=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCKbVHgZyi2A4D8S0JTtg3gM5oH00Q4WznkTjv27tur1PuKVr36Nw9qKH7RiQborUK1W+7xqxo6QjOE2urHXQYvVWifl1LX/d6BsuTd0d9C5KhXg8HaRyCHvrUVF+Jr6zR9UvNTf06WEiRdoAEiwqsb88TWhyq623fDuuIYI9HNAwIDAQAB
s1._domainkey.lbl.govk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0J4fnb0Oy1/oAAieADkAmvMnlrKh70wqhWVSxxgCJFn30npiZV6RoBytTS50nXgqD3l16c828xA+ynZVxpcatNWNtgVbaVtAZDTaHkkZwodVLNZFUgc/X86mOke33AJC2jg5FEaS0HggOiet4mCpudhVBRdi6F+o4+k/Kj0UyXBG6mLNCsaPbQIprdWA/pvRnLwPBT0HyYRj1forszajUkI8QNN7ICtvY8oJ/I/pvgoLmBj1p/kzWhvJyS1bgcWNLhx1ghacNj5oxYAtDtm8fVX+wp4Ti3JdDRFRsd8OlXPBnGZKnKtBta49nkpypWOa4048+Vq5chJnGSubBRCNBwIDAQAB
s2._domainkey.lbl.govk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxvDWnvZHkIHI969+nm/pIb9UnNafDSBOeYYl6Q9Eo8ei6Vmc1rpC+6OzaGK0GNRJU2Ftqvjx6dXAueZITqFOYqZ2BrTRP1D/3K/49TyFOdhqRpJXvH4lrYrWZF+cHQ2GoiFQ7U1sp8i6Tr3+I7lDFk6XazONSLfDXbE0L8Ru4q1IljqNdj76jG2g/CZbs2nzdrBRKRJrzlWZM+PHuUd0GSA7g3p7FqJEFsfFHibBXvU/iw1g0pPYVRSda+1WonNdpNJP0xp/mukY58ochfTSuUhZnrwrOOGv0R+E17ZdospRYMz3L6YuXq64OnX7AtasDixC1daXK6mAY0LcX6BLVQIDAQAB

Related IP addresses

IPv4 addresses used by lbl.gov: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
131.243.228.58Website131.243.228.0/24
131.243.5.53Name server adns.lbl.gov131.243.5.0/24
192.188.22.52Name server adns2.es.net192.188.22.0/24
192.188.22.22Name server adns1.es.net192.188.22.0/24
142.250.110.27Mail server aspmx.l.google.com142.250.110.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24
172.253.148.27Mail server alt3.aspmx.l.google.com172.253.148.0/24
198.124.252.166Authorized by SPF198.124.252.0/24
198.129.252.90Authorized by SPF198.129.252.0/24

WHOIS of the domain lbl.gov

Domain Name: lbl.gov
Registrar WHOIS Server: whois.nic.gov
Registrar URL: https://get.gov
Updated Date: 2026-08-14T17:00:00Z
Creation Date: 1997-10-02T01:29:25Z
Registry Expiry Date: 2027-08-28T20:12:23Z
Registrar: get.gov
Registrar IANA ID: 8888888
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Department of Energy
Registrant Street: REDACTED FOR PRIVACY
Registrant City: Berkeley
Registrant State/Province: CA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Email: REDACTED FOR PRIVACY
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Registry Security ID: REDACTED FOR PRIVACY
Security Name: REDACTED FOR PRIVACY
Security Organization: REDACTED FOR PRIVACY
Security Street: REDACTED FOR PRIVACY
Security City: REDACTED FOR PRIVACY
Security State/Province: REDACTED FOR PRIVACY
Security Postal Code: REDACTED FOR PRIVACY
Security Country: REDACTED FOR PRIVACY
Security Phone: REDACTED FOR PRIVACY
Security Email: [email protected]
Name Server: adns.lbl.gov
Name Server: adns1.es.net
Name Server: adns2.es.net
DNSSEC: signedDelegation
>>> Last update of WHOIS database: 2026-10-01T17:47:50Z <<<

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

WHOIS information is provided by the registry solely for query-based,
informational purposes. Any information provided is "as is" without any
guarantee of accuracy. You may not use such information to (a) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations; (b) enable high volume, automated,
electronic processes that access the registry's systems or any
ICANN-Accredited Registrar, except as reasonably necessary to register
domain names or modify existing registrations; or (c) engage in or support
unlawful behavior. We reserve the right to restrict or deny your access to
the WHOIS database, and may modify these terms at any time.

% Query time: 508 msec
% WHEN: Thu Oct 01 17:47:49 UTC 2026