Summary
- Registrar
- MarkMonitor Inc.
- Status
- clientTransferProhibited
- Created on
- June 22, 2005
- Expires on
- January 2, 2027
- Name servers
- ns3.google.com, ns4.google.com, ns2.google.com, ns1.google.com
- Mail servers
- —
- DMARC
- Reject
- SPF
- Strict
- 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 goo.gl 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; rua=mailto:[email protected]
Authorized senders (SPF)
E-mails sent by any other server are rejected.
SPF lists the servers allowed to send e-mails for goo.gl.
| Rule | Value | Result |
|---|---|---|
| all | — | Rejected |
Top-level DNS lookups: 0 of 10 allowed
Record
v=spf1 -all
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 goo.gl arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from goo.gl 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 @goo.gl 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
goo.gl MX 10 mx1.goo.gl. goo.gl MX 20 mx2.goo.gl.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.goo.gl.
- 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
goo.gl 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.goo.gl, 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.goo.gl 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.goo.gl, 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.goo.gl 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 goo.gl
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 | 172.217.22.46 |
| AAAA | 2a00:1450:4007:816::200e |
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 |
|---|---|
| ns3.google.com | 216.239.36.10 |
| ns4.google.com | 216.239.38.10 |
| ns2.google.com | 216.239.34.10 |
| ns1.google.com | 216.239.32.10 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @goo.gl 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.
No mail server: the domain does not receive e-mails.
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.goo.gl.
| Name | Content |
|---|---|
| goo.gl | facebook-domain-verification=7o3yquoyjiue2na6brk0mxzcxqb9w7 |
| goo.gl | v=spf1 -all |
| _dmarc.goo.gl | v=DMARC1; p=reject; rua=mailto:[email protected] |
Related IP addresses
IPv4 addresses used by goo.gl: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 172.217.22.46 | Website | 172.217.22.0/24 |
| 216.239.36.10 | Name server ns3.google.com | 216.239.36.0/24 |
| 216.239.38.10 | Name server ns4.google.com | 216.239.38.0/24 |
| 216.239.34.10 | Name server ns2.google.com | 216.239.34.0/24 |
| 216.239.32.10 | Name server ns1.google.com | 216.239.32.0/24 |
WHOIS of the domain goo.gl
Domain Name: GOO.GL Registry Domain ID: D327742570-CNIC Registrar WHOIS Server: whois.markmonitor.com Registrar URL: Updated Date: 2026-01-01T16:02:36.0Z Creation Date: 2005-06-22T02:00:00.0Z Registry Expiry Date: 2027-01-01T23:59:59.0Z Registrar: MarkMonitor Inc. Registrar IANA ID: 292 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Registrant Email: https://whois.nic.gl/contact/goo.gl/registrant Tech Email: https://whois.nic.gl/contact/goo.gl/tech Name Server: NS1.GOOGLE.COM Name Server: NS2.GOOGLE.COM Name Server: NS3.GOOGLE.COM Name Server: NS4.GOOGLE.COM DNSSEC: unsigned Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.2083895740 URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T01:28:55.0Z <<< For more information on Whois status codes, please visit https://icann.org/epp The registration data available in this service is limited. Additional data may be available at https://lookup.icann.org The Whois and RDAP services are provided by CentralNic, and contain information pertaining to Internet domain names registered by our our customers. By using this service you are agreeing (1) not to use any information presented here for any purpose other than determining ownership of domain names, (2) not to store or reproduce this data in any way, (3) not to use any high-volume, automated, electronic processes to obtain data from this service. Abuse of this service is monitored and actions in contravention of these terms will result in being permanently blacklisted. All data is (c) CentralNic Ltd (https://www.centralnicregistry.com) Access to the Whois and RDAP services is rate limited. For more information, visit https://centralnicregistry.com/policies/whois-guidance. Domain Name: goo.gl Registry Domain ID: Registrar WHOIS Server: whois.markmonitor.com Registrar URL: http://www.markmonitor.com Updated Date: 2025-12-02T01:11:38+0000 Creation Date: 2005-06-16T07:00:00+0000 Registrar Registration Expiration Date: 2027-01-01T00:00:00+0000 Registrar: MarkMonitor, Inc. Registrar IANA ID: 292 Registrar Abuse Contact: https://corp.markmonitor.com/domain/ui/abuse-report Registrar Abuse Contact Phone: +1.2086851750 Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited) Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited) Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited) Registrant Organization: Google LLC Registrant Country: US Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/goo.gl Name Server: ns3.google.com Name Server: ns2.google.com Name Server: ns4.google.com Name Server: ns1.google.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-10-01T01:24:08+0000 <<< For more information on WHOIS status codes, please visit: https://www.icann.org/resources/pages/epp-status-codes If you wish to contact this domain’s Registrant or Technical contact, and such email address is not visible above, you may do so via our web form, pursuant to ICANN’s Temporary Specification. To verify that you are not a robot, please enter your email address to receive a link to a page that facilitates email communication with the relevant contact(s). Web-based WHOIS: https://domains.markmonitor.com/whois/contact/goo.gl If you have a legitimate interest in viewing the non-public WHOIS details, send your request and the reasons for your request to [email protected] and specify the domain name in the subject line. We will review that request and may ask for supporting documentation and explanation. The data in MarkMonitor’s WHOIS database is provided for information purposes, and to assist persons in obtaining information about or related to a domain name’s registration record. While MarkMonitor believes the data to be accurate, the data is provided "as is" with no guarantee or warranties regarding its accuracy. By submitting a WHOIS query, you agree that you will 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 by email, telephone, or facsimile of mass, unsolicited, commercial advertising, or spam; or (2) enable high volume, automated, or electronic processes that send queries, data, or email to MarkMonitor (or its systems) or the domain name contacts (or its systems). MarkMonitor reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. MarkMonitor Domain Management(TM) Protecting companies and consumers in a digital world. Visit MarkMonitor at https://www.markmonitor.com Contact us at +1.8007459229 In Europe, at +44.02032062220 -- % Query time: 832 msec % WHEN: Thu Oct 01 01:28:55 UTC 2026