Hostname
jiobit.com
Last fetched
jiobit.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. jiobit.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
No IPv4 resolution is recorded for jiobit.com in WhisperGraph.
IPv6 resolution
No AAAA record for jiobit.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of jiobit.com owner
- Contact emails
- 48d56dad0a28fd23231db5837120503d@domaindiscreet.com, 58103325@myprivatename.com, 6selnpbbq8h6cap1pekb0hgtho@domaindiscreet.com, john_renaldi@yahoo.com, 03092065-4352-4c1e-a3c6-be95c913e3ce@identity-protect.org, 0e6a96d1-5dae-421a-91ce-2b485bf5abd4@identity-protect.org, 2c5fa84c-4a59-460e-9b66-99ec599b337f@identity-protect.org, 55afa717-ec97-40c9-b86c-a72edef4807f@identity-protect.org, c30c8691-771f-42cf-805f-8e0e3d651249@identity-protect.org, f5298b04-6bfd-4cc3-8190-8178b5220918@identity-protect.org
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
Mail and authentication
Nameservers
- lakas.ns.cloudflare.com
- paige.ns.cloudflare.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- mxa-0096d201.gslb.pphosted.com
- mxb-0096d201.gslb.pphosted.com
SPF policy
- include: _spf.firebasemail.com
- include: _spf.google.com
- include: shops.shopify.com
- include: mail.zendesk.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from jiobit.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: "jiobit.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.