Hostname
joytours.gr
Last fetched
joytours.gr resolves to 104.26.8.206, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. joytours.gr is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.26.8.206
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.9.206
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.74.20
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for joytours.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 |
|---|
| cpanel.joytours.gr |
| cpcalendars.joytours.gr |
| cpcontacts.joytours.gr |
| mail.joytours.gr |
| mail2.joytours.gr |
| old.joytours.gr |
| webdisk.joytours.gr |
| webmail.joytours.gr |
| www.joytours.gr |
Showing 9 of 9 subdomains (9 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
- rafe.ns.cloudflare.com
- zac.ns.cloudflare.com
- 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
MX records
- mail.joytours.gr
- mail2.joytours.gr
- mail.d607122.name-servers.gr
SPF policy
- a: joytours.gr
- mx: joytours.gr
- include: spf.em.secureserver.net
- ip: 148.251.75.180
- ip: 185.25.20.187
- ip: 185.25.23.99
Threat-feed evidence
History
Related pages
Pivot from joytours.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: "joytours.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.