Skip to content

Hostname

traktorpool.lv

Last fetched

traktorpool.lv resolves to 212.101.210.155, announced in 212.101.192.0/19 by DTS-Systeme-Muenster - DTS Systeme Muenster GmbH in DE. traktorpool.lv 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 · traktorpool.lvRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/traktorpool.lv

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for traktorpool.lv. 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
admin.traktorpool.lv
analytics.traktorpool.lv
connect.traktorpool.lv
development.traktorpool.lv
gql.traktorpool.lv
sandbox.traktorpool.lv
secure.traktorpool.lv
staging.traktorpool.lv
widgetgenerator.traktorpool.lv
www.traktorpool.lv

Showing 10 of 15. 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

  • ns3.icsmedia.de
  • ns4.icsmedia.de

MX records

  • traktorpool-lv.mail.protection.outlook.com

SPF policy

  • ip: 212.101.207.0/24
  • ip: 212.101.210.0/24
  • ip: 10.3.1.50/24
  • a: mailer1.citycom-austria.com
  • a: mailer2.citycom-austria.com
  • a: w018e83b.kasserver.com
  • include: spf.protection.outlook.com
  • include: spf.friends-braunschweig.de
  • mx: traktorpool.lv
  • ip: 213.188.99.147
  • ip: 87.118.83.100

Threat-feed evidence

History

Related pages

Pivot from traktorpool.lv 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: "traktorpool.lv"})-[: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.