Summary
- Registrar
- Key-Systems GmbH
- Status
- clientDeleteProhibited
- Created on
- September 18, 2017
- Expires on
- September 18, 2027
- Name servers
- ns-1741.awsdns-25.co.uk, ns-1116.awsdns-11.org, ns-956.awsdns-55.net, ns-224.awsdns-28.com
- Mail servers
- aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
- DMARC
- Reject
- SPF
- Strict
- DKIM
- 1 key found
- 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 greynoise.io 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 greynoise.io.
| Rule | Value | Result |
|---|---|---|
| include | amazonses.com | Allowed |
| include | stspg-customer.com | Allowed |
| include | _spf.google.com | Allowed |
| include | 4282754.spf07.hubspotemail.net | Allowed |
| all | — | Rejected |
Top-level DNS lookups: 4 of 10 allowed
Record
v=spf1 include:amazonses.com include:stspg-customer.com include:_spf.google.com include:4282754.spf07.hubspotemail.net -all
E-mail signing (DKIM)
DKIM keys published by greynoise.io under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| Google Workspace | RSA 2048 bits | Active |
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 greynoise.io arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from greynoise.io 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 @greynoise.io 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
greynoise.io MX 10 mx1.greynoise.io. greynoise.io MX 20 mx2.greynoise.io.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.greynoise.io.
- 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
greynoise.io 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.greynoise.io, 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.greynoise.io 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.greynoise.io, 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.greynoise.io 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 greynoise.io
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 | 198.202.211.1 |
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 |
|---|---|
| ns-1741.awsdns-25.co.uk | 205.251.198.205 |
| ns-1116.awsdns-11.org | 205.251.196.92 |
| ns-956.awsdns-55.net | 205.251.195.188 |
| ns-224.awsdns-28.com | 205.251.192.224 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @greynoise.io 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 |
|---|---|---|
| 1 | aspmx.l.google.com | 172.253.143.27 |
| 5 | alt1.aspmx.l.google.com | 192.178.213.27 |
| 5 | alt2.aspmx.l.google.com | 142.251.127.27 |
| 10 | alt4.aspmx.l.google.com | 142.250.147.27 |
| 10 | alt3.aspmx.l.google.com | 172.253.148.26 |
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.greynoise.io.
| Name | Content |
|---|---|
| greynoise.io | canva-site-verification=jkcqgJvW0x5vOsYmFInmUg |
| greynoise.io | google-site-verification=GwEgq_50jwkMm3M5EIcsrbW35WmG2mrgnbQS6YHiC-g |
| greynoise.io | status-page-domain-verification=p8b6lc0jd1rm |
| greynoise.io | censys-domain-verification=yCcVk71tGFet63dpDivqyLnbd7VlxRuOX6GusT_BgN5A |
| greynoise.io | google-site-verification=pWuTXIYtpgtiMv82mzc6KxfapOV6_5A1AeoKhIQy1FE |
| greynoise.io | MS=ms40094720 |
| greynoise.io | v=spf1 include:amazonses.com include:stspg-customer.com include:_spf.google.com include:4282754.spf07.hubspotemail.net -all |
| greynoise.io | uber-domain-verification=3f2be1ad-0a56-4e08-9a92-3e6675f71795 |
| greynoise.io | cloudflare_dashboard_sso=cee54e6968b2b0d08a1bf17eb5d15e94 |
| greynoise.io | google-site-verification=K2ZPY-BMJyYQR0FQWh4fgXJFsBkp8aoaluxjDf3QYwg |
| greynoise.io | google-site-verification=DXUtZ52eq_mWDBroGFIM0O4jXcSjyLoTPQzRkhYChGU |
| greynoise.io | amp-domain-verification-ca1w9z=HvGe8IBqeIexhmGv9UNvAo8Yn |
| greynoise.io | stripe-verification=9EEC529B9BE3B480FA54DECEE49B143C7B87E18C44974EABF1D7EBB9D6B353B0 |
| greynoise.io | ZOOM_verify_timausM4We51RLx6rpjkBP |
| greynoise.io | postman-domain-verification=e0005d7bf7a1ddb4cae02bf76bb279da4a1c50132b3e9deb8083807edefee53e28aa5567ea53d8620d22542ed0b42b028946834cefb18afc210771dd944400f6 |
| greynoise.io | cursor-domain-verification-mwzfvk=4T4Ma4E09X6stQb87Ya9awqKt |
| greynoise.io | linear-domain-verification=yd6wnmg4rrgx |
| greynoise.io | google-site-verification=O8_77JYx8iQdAG0ubAzDx_08ZDVLvasRwIcmuuHY7eo |
| greynoise.io | openai-domain-verification=dv-9EYcrZw7f2ekjAkCQFqyBl4c |
| greynoise.io | anthropic-domain-verification-ys5xy0=p3lkk3dRAaVS6MtfhmUgFKq64 |
| greynoise.io | pendo-domain-verification=88c07dba-2f88-4989-8ea8-29d6718ba258 |
| greynoise.io | zapier-domain-verification-challenge=3a0ca847-d929-42c4-9915-1c317a1440c1 |
| _dmarc.greynoise.io | v=DMARC1; p=reject; rua=mailto:[email protected] |
| google._domainkey.greynoise.io | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsMGfsbPQrLab5DNT6D7lyXsHZdhAm3r4i41VikGmoCR6O8zXLLsqPH0PjQeYjlncE/XdZKoI9CiUgJcDevgTXUOnYd/VpDukgH7K7v/5WyByEgnBKA5+9UJ9YgiiofyN2OlK8Sj0to/hDsWmnC+kgCgn0PZANPmdtxSWjnd17KdUqb02rf4vbhV5txZVWKBveH93jxFTywP0lxX4G4dn7++R4f7YGGgIs53uq9h/IBHo+JOz5koQhwxKqAeNlMNPaNAQ8qVixy3e7oe4Lzu3xv2MKgQU25pO6hWeBN/ZFlj13MoEgf+QqGjntDkickZdrnutMT1wsw7InLXu3tlf+QIDAQAB |
Related IP addresses
IPv4 addresses used by greynoise.io: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 198.202.211.1 | Website | 198.202.211.0/24 |
| 205.251.198.205 | Name server ns-1741.awsdns-25.co.uk | 205.251.198.0/24 |
| 205.251.196.92 | Name server ns-1116.awsdns-11.org | 205.251.196.0/24 |
| 205.251.195.188 | Name server ns-956.awsdns-55.net | 205.251.195.0/24 |
| 205.251.192.224 | Name server ns-224.awsdns-28.com | 205.251.192.0/24 |
| 172.253.143.27 | Mail server aspmx.l.google.com | 172.253.143.0/24 |
| 192.178.213.27 | Mail server alt1.aspmx.l.google.com | 192.178.213.0/24 |
| 142.251.127.27 | Mail server alt2.aspmx.l.google.com | 142.251.127.0/24 |
| 142.250.147.27 | Mail server alt4.aspmx.l.google.com | 142.250.147.0/24 |
| 172.253.148.26 | Mail server alt3.aspmx.l.google.com | 172.253.148.0/24 |
WHOIS of the domain greynoise.io
Domain Name: greynoise.io Registry Domain ID: REDACTED Registrar WHOIS Server: whois.rrpproxy.net Registrar URL: http://key-systems.net Updated Date: 2026-09-09T08:50:09Z Creation Date: 2017-09-18T17:50:28Z Registry Expiry Date: 2027-09-18T17:50:28Z Registrar: Key-Systems GmbH Registrar IANA ID: 269 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +49.68949396850 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: c/o whoisproxy.com Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: VA Registrant Postal Code: REDACTED Registrant Country: US Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: REDACTED Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: REDACTED Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: REDACTED Name Server: ns-956.awsdns-55.net Name Server: ns-224.awsdns-28.com Name Server: ns-1116.awsdns-11.org Name Server: ns-1741.awsdns-25.co.uk DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T21:37:40Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The queried object does not exist: >>> Last update of WHOIS database: 2026-10-01T21:37:40Z <<< The data in the WHOIS database of Key-Systems GmbH is provided by Key-Systems GmbH for information purposes, and to assist persons in obtaining information about or related to domain name registration records. Key-Systems GmbH does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances, you will use this data to 1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via E-mail (spam); or 2) enable high volume, automated, electronic processes that apply to Key-Systems GmbH or its systems. Key-Systems GmbH reserves the right to modify these terms. By submitting this query, you agree to abide by this policy. % Query time: 671 msec % WHEN: Thu Oct 01 21:37:40 UTC 2026