Skip to content

Hostname

magnatuning.com

Last fetched

magnatuning.com resolves to 176.223.123.9, announced in 176.223.122.0/23 by Cyber_Folks-RO-DC_CLJ - Cyber_Folks SRL in RO. magnatuning.com 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 · magnatuning.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/magnatuning.com

Resolution chain

IPv6 resolution

No AAAA record for magnatuning.com is recorded in WhisperGraph.

Attribution

cyber folks

ORIGIN_AS

WHOIS identity

Registrar
iana:151
Registrant organisation
blenessy zoltan
Contact emails
info@privatename.com, zolll@yahoo.com

Subdomains

Subdomain
mail.magnatuning.com
www.magnatuning.com

Showing 2 of 2 subdomains (2 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

  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns1.cyberfolks.ro
  • ns2.cyberfolks.ro
  • ns3.cyberfolks.ro
  • ns4.cyberfolks.ro

MX records

  • spamguard1.mxserver.ro
  • spamguard2.mxserver.ro

SPF policy

  • a: magnatuning.com
  • mx: magnatuning.com
  • include: spf.mxserver.ro
  • ip: 176.223.123.9
  • ip: 188.212.156.35
  • ip: 31.14.13.227
  • ip: 89.44.47.55
  • ip: 95.214.133.208

Threat-feed evidence

History

Related pages

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