Skip to content

Hostname

corrently.de

Last fetched

corrently.de resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA.

Nutrition Label

WHISPER CANON · corrently.deRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/corrently.de

Resolution chain

corrently.de resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
104.21.42.42104.21.32.0/20AS13335CLOUDFLARENET - Cloudflare, Inc.CA
172.67.156.25172.67.144.0/20AS13335CLOUDFLARENET - Cloudflare, Inc.CA

WHOIS identity

No WHOIS records are currently associated with corrently.de in WhisperGraph.

Subdomains

33 observed subdomains of corrently.de.

Subdomain
app.corrently.de
casa.corrently.de
docs.corrently.de
fix.corrently.de
gsi.corrently.de
hostmaster.corrently.de
m.corrently.de
mail.corrently.de
marios.corrently.de
meet.corrently.de
portainer.corrently.de
premium.corrently.de
protect.corrently.de
shop.corrently.de
site.corrently.de
social.corrently.de
splash.corrently.de
squad.corrently.de
tree.corrently.de
webinar.corrently.de
wildcard.corrently.de
www.corrently.de

Showing 22 of 33. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from corrently.de in the public web crawl.

30 sites link to this hostname.

33 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

12 SPF mechanisms authorising senders for corrently.de.

MechanismTarget
SPF_Acorrently.de
SPF_INCLUDE_spf.google.com
SPF_INCLUDEcorrently.de
SPF_INCLUDEispgateway.de
SPF_INCLUDEpremium.corrently.de
SPF_INCLUDEsendgrid.net
SPF_INCLUDEshop.corrently.de
SPF_INCLUDEzoho.com
SPF_IP192.248.182.151
SPF_IP80.67.18.15/32
SPF_IP85.25.133.34
SPF_MXcorrently.de

Related pages

Pivot deeper into the graph from corrently.de.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "corrently.de"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.