Skip to content

Hostname

lovegraph.me

Last fetched

lovegraph.me resolves to 13.227.192.107, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. lovegraph.me 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 · lovegraph.meRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/lovegraph.me

Resolution chain

IPv6 resolution

No AAAA record for lovegraph.me is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
mixi,
Contact emails
privacy@whoisprivacyprotection.info

Subdomains

Subdomain
academy-plus.lovegraph.me
academy.lovegraph.me
anl.lovegraph.me
assets-cf.lovegraph.me
campaign.lovegraph.me
corporate-assets.lovegraph.me
corporate.lovegraph.me
dev.lovegraph.me
factory.lovegraph.me
help.lovegraph.me
leo-staging.lovegraph.me
leo.lovegraph.me

Showing 12 of 24. 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-399.awsdns-49.com
  • ns-582.awsdns-08.net
  • ns-1319.awsdns-36.org
  • ns-1742.awsdns-25.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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