Skip to content

Hostname

trg.de

Last fetched

trg.de resolves to 162.55.7.126, announced in 162.60.12.0/22 by HETZNER-AS - Hetzner Online GmbH in DE. trg.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 · trg.deRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint6.6/10canon.whisper.security/host/trg.de

Resolution chain

IPv6 resolution

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

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for trg.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
data.trg.de
dms.trg.de
home.trg.de
matomo.trg.de
native.trg.de
nativeads.trg.de
s2s.trg.de
share.trg.de
srv.trg.de
staging.trg.de
www.trg.de

Showing 11 of 11 subdomains (11 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • ns.inwx.de
  • ns2.inwx.de
  • a.nic.de
  • f.nic.de
  • z.nic.de
  • ns3.inwx.eu
  • l.de.net
  • n.de.net
  • s.de.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • ip: 136.243.54.162/32
  • include: _spf.google.com
  • include: _spf.psm.knowbe4.com
  • include: spf.neory.com
  • include: teamworkdesk.com
  • a: trg.de
  • mx: trg.de

Threat-feed evidence

History

Related pages

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