Skip to content

Hostname

javryo.com

Last fetched

javryo.com resolves to 104.21.43.163, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. javryo.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 · javryo.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/javryo.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
d48f355a57c8474da3e2639d281d085d.protect@whoisguard.com, 010ee3e388d44cf58c2754dd19bf9543.protect@withheldforprivacy.com, 78664b50359d4d58ab40c558db6dc296.protect@withheldforprivacy.com

Subdomains

Subdomain
cpanel.javryo.com
cpcalendars.javryo.com
cpcontacts.javryo.com
mail.javryo.com
new.javryo.com
webdisk.javryo.com
webmail.javryo.com
www.javryo.com

Showing 8 of 9. 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

  • coraline.ns.cloudflare.com
  • matias.ns.cloudflare.com
  • ns1.vicerocks.com
  • ns2.vicerocks.com

MX records

  • javryo.com
  • _dc-mx.0dfcf217a3f2.javryo.com

SPF policy

  • include: spf.antispamcloud.com
  • a: javryo.com
  • mx: javryo.com
  • ip: 103.123.62.41
  • ip: 103.129.220.6
  • ip: 167.88.50.7
  • ip: 172.99.249.179
  • ip: 185.224.81.210
  • ip: 185.224.81.3
  • ip: 209.126.86.114

Threat-feed evidence

History

Related pages

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