Skip to content

Hostname

horizonsingles.com

Last fetched

horizonsingles.com resolves to 34.111.31.218, announced in 34.108.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. horizonsingles.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 · horizonsingles.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/horizonsingles.com

Resolution chain

IPv6 resolution

No AAAA record for horizonsingles.com is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
alex esquerra
Contact emails
admin@onamae.com, alex_esquerra@yahoo.com, proxy@whoisprotectservice.com, 09ea4c4a7d@horizonsingles.com.whoistrustee.com, 564c9861ae282e26f1f366d9354684dcd2880061cd143b8b3db3ef8d6ce3ca4d@horizonsingles.com.whoisproxy.org, 69647b99a1ad5dd6d7df36107b58a5e9192033cd23e174299f0d1aa3b912ff83@horizonsingles.com.whoisproxy.org, 6cfc430b34c6c8f3e262d4f2e2f160552443ee28550200ff01253dd10ad04cd8@horizonsingles.com.whoisproxy.org, 897dd789550aed0b69b099a6d989bae1cba525a2ba517bea1c2fd648330a0cfb@horizonsingles.com.whoisproxy.org, b2ff02de8c3a600a717f276f779ee0ce0eca3210adb1b56cd84181ce8490c0e1@horizonsingles.com.whoisproxy.org

Subdomains

Subdomain
acc.horizonsingles.com
cdn.horizonsingles.com
delivery.horizonsingles.com

Showing 3 of 4. View all subdomains →

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.net
  • ns4.dnsimple-edge.org

MX records

  • mx1.giganticgerbil.com

SPF policy

  • include: spf.giganticgerbil.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

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