Skip to content

Hostname

funjoy-technology.net

Last fetched

funjoy-technology.net resolves to 13.227.192.21, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. funjoy-technology.net 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 · funjoy-technology.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/funjoy-technology.net

Resolution chain

IPv6 resolution

No AAAA record for funjoy-technology.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
identity protection service
Contact emails
3d1ba2a6-2ae3-4507-a276-fbf2d6c7c333@identity-protect.org, 5b4d7f47-f572-4158-b501-d6968adbd46c@identity-protect.org, 61661401-2907-4d30-9b01-1114468ef1d9@identity-protect.org, 63d53e37-9e1c-41ab-84e1-e8347670acb5@identity-protect.org, 8e48e1a0-05f0-4016-9955-e630bc6a3721@identity-protect.org, cde2d0e0-f60c-4d09-b94e-e1c1013aba92@identity-protect.org, f1edb892-8d57-44f0-a3a0-75f91995d24f@identity-protect.org, owner-6137362@funjoy-technology.net.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-349.awsdns-43.com
  • ns-620.awsdns-13.net
  • 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-1300.awsdns-34.org
  • ns-1714.awsdns-22.co.uk

MX records

  • inbound-smtp.us-west-2.amazonaws.com

SPF policy

  • include: amazonses.com

Threat-feed evidence

History

Related pages

Pivot from funjoy-technology.net 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: "funjoy-technology.net"})-[: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.