Skip to content

Hostname

vilkasgroup.com

Last fetched

vilkasgroup.com resolves to 199.60.103.185, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. vilkasgroup.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 · vilkasgroup.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/vilkasgroup.com

Resolution chain

IPv6 resolution

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

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
iana:1052
Registrant organisation
korkiakoski markku
Contact emails
support@vilkas.fi, techsupport@vilkas.fi, tuki@vilkas.fi

Subdomains

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

Mail and authentication

Nameservers

  • ns-d.eurodns.biz
  • ns-a.eurodns.com
  • ns-c.eurodns.eu
  • 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
  • ns-b.eurodns.org

MX records

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

SPF policy

  • include: _spf.google.com
  • include: spf.lianamailer.com
  • include: spf.mandrillapp.com
  • include: stspg-customer.com
  • a: vilkasgroup.com
  • include: _spf.omaverkkokauppa.fi
  • include: spf.amazee.io
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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