Skip to content

Hostname

e-masters.de

Last fetched

e-masters.de resolves to 83.246.49.40, announced in 83.246.49.0/24 by SSERV-AS - kyberio GmbH in DE. e-masters.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 · e-masters.deRouting diversity1.5/10Peering density5.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/e-masters.de

Resolution chain

IPv6 resolution

No AAAA record for e-masters.de is recorded in WhisperGraph.

Attribution

kyberio

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for e-masters.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
app.e-masters.de
baustein.e-masters.de
beispiel21.e-masters.de
beispiel21shk.e-masters.de
beispiel22.e-masters.de
beispiel22shk.e-masters.de
beispielhomepage.e-masters.de
beispielhomepageshk.e-masters.de
beispielhpk.e-masters.de
beispielminimalistisch.e-masters.de
beispielonepager.e-masters.de
beispielonepagereee.e-masters.de

Showing 12 of 42. 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

  • ns31.domaincontrol.com
  • ns32.domaincontrol.com

MX records

  • mail.mitegro.de
  • emasters-de0c.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: _spf.sendnode.com
  • mx: e-masters.de
  • include: spf.evidenz.de
  • include: 25735866.spf10.hubspotemail.net
  • a: bulk.mitegro.net

Threat-feed evidence

History

Related pages

Pivot from e-masters.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: "e-masters.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.