Skip to content

Hostname

bingeniousgroup.com

Last fetched

bingeniousgroup.com resolves to 216.75.62.10, announced in 216.75.0.0/18 by CARINET - CariNet, Inc. in US. bingeniousgroup.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 · bingeniousgroup.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/bingeniousgroup.com

Resolution chain

IPv6 resolution

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

Attribution

carinet

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:93
Registrant organisation
dkbyte
Contact emails
0e9078c4242c5e0e2132eafcd36ac1ca7910e326@privatedomain.gkg.net, 1112269c665bc4e8436bf2917b278849355a5730@privatedomain.gkg.net, 1dfd0eb935cf3d83c6dd35e0b391e4462ec6a9cc@privatedomain.gkg.net, 47bf902b2b62563aeb3df26f269e15d0343b0195@privatedomain.gkg.net, 48b410a1f828073c235b4fd91aeea44f8b17a0b3@privatedomain.gkg.net, 4a77c0e1bf885dda1216feae3f48c7c2e12ca929@privatedomain.gkg.net, 603338be02c433b9d3462ab47df2e63c951db957@privatedomain.gkg.net, 881b5f964105954cbb31989e9ad3ef5d811de15e@privatedomain.gkg.net, 94842ec4668b6c32aee64067f730f6cc2015a935@privatedomain.gkg.net, e251ff75d3a6fdae3ecb42ee997fdc280f1153b2@privatedomain.gkg.net, e47ab53d801dd27805c92234f96dd9ae8e398212@privatedomain.gkg.net, f72535c2ae3aa7cdb0440c5c1f146a1d48f911f9@privatedomain.gkg.net

Subdomains

Mail and authentication

Nameservers

  • ns1.hostingecuador.net
  • ns2.hostingecuador.net

MX records

  • bingeniousgroup.com

SPF policy

  • a: bingeniousgroup.com
  • mx: bingeniousgroup.com
  • ip: 216.75.62.10

Threat-feed evidence

History

Related pages

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