Skip to content

Hostname

egencia.de

Last fetched

egencia.de resolves to 194.36.55.251, announced in 194.36.55.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in GB. egencia.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · egencia.deRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/egencia.de

Resolution chain

IPv6 resolution

No AAAA record for egencia.de is recorded in WhisperGraph.

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for egencia.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
autodiscover.egencia.de
cde.egencia.de
client-reports.egencia.de
corporate.egencia.de
lyncaccess.egencia.de
lyncdiscover.egencia.de
lyncphaccess.egencia.de
metrics.egencia.de
mice.egencia.de
mobile.egencia.de
randstad.egencia.de
reporting.egencia.de

Showing 12 of 18. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns-356.awsdns-44.com
  • ns-930.awsdns-52.net
  • ns-1030.awsdns-00.org
  • ns-1761.awsdns-28.co.uk

MX records

  • mxa-0057e501.gslb.pphosted.com
  • mxb-0057e501.gslb.pphosted.com

SPF policy

  • include: _spf.egencia.com
  • include: spf.mandrillapp.com
  • include: mktomail.com
  • include: spf-0057e501.pphosted.com
  • include: spf-0057e504.pphosted.com

Threat-feed evidence

History

Related pages

Pivot from egencia.de into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

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

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