Hostname
bzinga.com
Last fetched
bzinga.com resolves to 3.108.102.149, announced in 3.108.0.0/14 by AMAZON-02 - Amazon.com, Inc. in IN. bzinga.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 3.108.102.149
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.108.88.126
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.111.177.243
3.108.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 3.6.14.174
3.6.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 43.205.197.23
43.204.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
- 65.0.70.24
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
IPv6 resolution
No AAAA record for bzinga.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- client 32780
- Contact emails
- domains@hugedomains.com, mohandas.nair@zee.com, 1eeab483-8bff-490e-8b4e-517e84ff6529@identity-protect.org, 2de9f0e1-4e37-4d6d-97ec-a8e90265350b@identity-protect.org, bd005ae9-38a3-42a4-8b58-2ff5ce15d654@identity-protect.org, dab9036e-8892-4c01-b018-e2afc802ccc1@identity-protect.org, owner-11971496@bzinga.com.whoisprivacyservice.org
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-394.awsdns-49.com
- ns-921.awsdns-51.net
- ns-1162.awsdns-17.org
- ns-1924.awsdns-48.co.uk
MX records
- mail.bzinga.com
- bzinga-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- include: transmail.net.in
- include: zoho.in
- include: one.zoho.in
- include: mail.zohoanalytics.in
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from bzinga.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: "bzinga.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.