Skip to content

Hostname

veto.gr

Last fetched

veto.gr resolves to 172.66.40.89, announced in 172.66.40.0/21 by CLOUDFLARENET - Cloudflare, Inc. in CA. veto.gr 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 · veto.grRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/veto.gr

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for veto.gr. 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
aek.veto.gr
arena.veto.gr
arena2.veto.gr
arenaregistration.veto.gr
babolat.veto.gr
babolat2.veto.gr
cloud.veto.gr
college.veto.gr
collegestore2.veto.gr
coros.veto.gr
coros2.veto.gr
cs.veto.gr

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

Sample outbound links

Mail and authentication

Nameservers

  • galileo.veto.gr
  • july.veto.gr
  • medusa.veto.gr
  • venus.veto.gr

MX records

  • filter10.antispamcloud.com
  • filter20.antispamcloud.com
  • filter30.antispamcloud.com
  • filter40.antispamcloud.com

SPF policy

  • include: spf.antispamcloud.com
  • include: spfa.mailendo.com
  • include: mail.zendesk.com
  • a: veto.gr
  • mx: veto.gr
  • include: servers.mcsv.net
  • ip: 185.134.112.187
  • ip: 185.134.112.216
  • ip: 185.134.112.217
  • ip: 185.134.113.230
  • ip: 185.134.114.122
  • ip: 62.1.26.19

Threat-feed evidence

History

Related pages

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