Dataweaz

efg.gg

Summary

Registrar
—
Status
Active
Created on
November 25, 2021
Expires on
—
Name servers
jerry.ns.cloudflare.com, angela.ns.cloudflare.com
Mail servers
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.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 efg.gg but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=reject; pct=100; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=s; aspf=r; fo=1; rf=afrf; ri=3600

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 efg.gg.

RuleValueResult
include_u.efg.gg._spf.smart.ondmarc.comAllowed
includemg-spf.greenhouse.ioAllowed
all—Suspicious

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:_u.efg.gg._spf.smart.ondmarc.com include:mg-spf.greenhouse.io ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
mail—RSA 1024 bits · shortActive

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

efg.gg  MX  10 mx1.efg.gg.
efg.gg  MX  20 mx2.efg.gg.

What the record contains

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

efg.gg  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.efg.gg, 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.efg.gg  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.efg.gg, 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.efg.gg  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 efg.gg

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
A162.159.135.42
A162.159.134.42
AAAA2606:4700:7::a29f:872a
AAAA2606:4700:7::a29f:862a

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
jerry.ns.cloudflare.com173.245.59.182
angela.ns.cloudflare.com108.162.192.65

Mail servers (MX)

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

NameContent
efg.gg00D0Y000001Ijz0=1TBaa00000000EX
efg.ggcursor-domain-verification-e2s8w9=747tnK3ZL8cbBJw6qnXxnsuNF
efg.ggv=spf1 include:_u.efg.gg._spf.smart.ondmarc.com include:mg-spf.greenhouse.io ~all
efg.ggatlassian-domain-verification=mwN8H0E79ucSA37CMahsp6fQhc4CplRtepKc9USUUPlA86Kgu1IHZYK3dodjFDv/
efg.ggcursor-domain-verification-0hwyqz=iUpMlqhqbFpWRdhfqRyI6B5TZ
efg.ggopenai-domain-verification=dv-2C8Q09UQTGmJ0h4Vv1YSJVLE
efg.ggparsec-domain-verification=td_2WFdh9TXOB9mTdZ1UT0X9ymmWf6
efg.ggfigma-domain-verification=12362cd28675b9aeec04cad51aa2b3069703a376f63360a37b3c9bd30e23f089-1778238205
efg.gggoogle-site-verification=6cP7sNGvWMH_6uUrlR39UOU4bYUd8VgCsxX9-iEkyz0
efg.ggZXNsZmFjZWl0
efg.gglucid-verification=z95oghbwk3qprkc14h3p
efg.ggmiro-verification=cfdcb8eff3e54413506b541f74e93d8c41bdd638
efg.ggmongodb-site-verification=DzJo91MbE74gPzw1oGtMK3ZfhHPZTqrb
efg.ggh1-domain-verification=iuPDBmh88JJPAmRNtVQvroJUrxVULmqkp2EqRHEaamfoEZTX
efg.ggmixpanel-domain-verify=55ab63d6-3f7a-4308-9100-95e3b0d9265a
efg.ggpostman-domain-verification=297b56c1403ac4a46c04ea255a5bf5a3c8f6c0b56457491fc85d0e021873d86a7f71ffd4d5309ac32389ceed9c10dd85080e9e8299f38065bb3f2555390379f0
efg.ggdocusign=2660feaf-6da8-4ed6-813e-ade2cd936bd1
efg.ggwiz-domain-verification=1917bd75ef00aa87ce9e618d36cd68c81cca6e60873ed95149e88604523e7648
efg.ggdocusign=2ad38f86-8f7b-4b35-981a-97aace08dcf7
efg.gganthropic-domain-verification-hqhewd=fYxrfnULqbfrGKYDynPePWzk1
efg.ggca3-5812ce7335794cdc89a74d416852f1c5
efg.ggapple-domain-verification=wT6Z5XqPjyknfGqI
efg.ggatlassian-sending-domain-verification=7d3fe4e5-2f05-4a9f-911e-568bdbae1cf9
efg.ggZOOM_verify_L4gjW9E52IEYvYzPUYqci4
efg.ggdocusign=0f347204-f8d5-4e48-aa4b-afb12567da78
efg.ggautodesk-domain-verification=BPrUa7jDEMhHPhuxwxrD
efg.ggbrevo-code:6ef1bdca0140128a0b0cdffd769c529f
efg.ggMS=ms36474845
efg.ggdocusign=4c37c5ea-f244-4b0e-8b48-b24f0e4c341c
efg.ggsnowflake-verification=9ffaae43-01a0-1000-8008-000000000bbc
efg.ggmgverify=c4a5ded431fdb0dd10f1504155601333b3f44c61a785ddc77ae3ffe13e0ccc71
efg.gglovable_verification=wDwUZd8cAjIxpRFSEW6y
_dmarc.efg.ggv=DMARC1; p=reject; pct=100; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=s; aspf=r; fo=1; rf=afrf; ri=3600
google._domainkey.efg.ggv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCGoIYpy15q7TvX5gn4NmdoFI7uWQ1wY9zduw8hexIItykmbPMwjOhnF24EJ+nM8Sl/Q+AAEGk4JS7MVx3ZuboWHRrHJ94y3q9e1WFw7gvMoLAStXsGMlO/MTLZL5KEQaPoqqg/oLbF32uR2b2KuWhyxUdp56xGTDLn1WvYYtDGRwIDAQAB
mail._domainkey.efg.ggk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB

Related IP addresses

IPv4 addresses used by efg.gg: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
162.159.135.42Website162.159.135.0/24
162.159.134.42Website162.159.134.0/24
173.245.59.182Name server jerry.ns.cloudflare.com173.245.59.0/24
108.162.192.65Name server angela.ns.cloudflare.com108.162.192.0/24
142.250.110.27Mail server aspmx.l.google.com142.250.110.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
172.253.148.27Mail server alt3.aspmx.l.google.com172.253.148.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24

WHOIS of the domain efg.gg

Domain:
     efg.gg

Domain Status:
     Active
     Transfer Prohibited by Registrar

Registrant:
     ESL Gaming GmbH

Registrar:
     INWX GmbH (https://www.inwx.com)

Relevant dates:
     Registered on 25th November 2021 at 14:35:58.741
     Registry fee due on 25th November each year

Registration status:
     Registered until cancelled

Name servers:
     angela.ns.cloudflare.com
     jerry.ns.cloudflare.com
     

WHOIS lookup made on Thu, 1 Oct 2026 at 18:48:56 BST

This WHOIS information is provided for free by CIDR, operator of
the backend registry for domain names ending in GG and JE.

Copyright (c) and database right Island Networks 1996 - 2026.

You may not access this WHOIS server or use any data from it except
as permitted by our Terms and Conditions which are published
at http://www.channelisles.net/legal/whoisterms

They include restrictions and prohibitions on

- using or re-using the data for advertising;
- using or re-using the service for commercial purposes without a licence;
- repackaging, recompilation, redistribution or reuse;
- obscuring, removing or hiding any or all of this notice;
- exceeding query rate or volume limits.

The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

% Query time: 353 msec
% WHEN: Thu Oct 01 17:48:56 UTC 2026