Skip to content

Hostname

enerjoy.life

Last fetched

enerjoy.life resolves to 13.226.244.113, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. enerjoy.life 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 · enerjoy.lifeRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/enerjoy.life

Resolution chain

IPv6 resolution

No AAAA record for enerjoy.life is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
enerjoy pte.

Subdomains

Subdomain
af.enerjoy.life
ama-cp.enerjoy.life
cdn.enerjoy.life
cp.enerjoy.life
fnw-cp.enerjoy.life
meplus-account.enerjoy.life
shuteye-account.enerjoy.life
testsolution.enerjoy.life
tool.enerjoy.life
ts.enerjoy.life
www.enerjoy.life

Showing 11 of 15. 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

  • ns-364.awsdns-45.com
  • ns-712.awsdns-25.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-1329.awsdns-38.org
  • ns-1852.awsdns-39.co.uk

MX records

  • enerjoy-life.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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