Hostname
enbon.com
Last fetched
enbon.com resolves to 155.102.1.27, announced in 155.102.1.0/24 by Taobao - Zhejiang Taobao Network Co.,Ltd in SG. enbon.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
- unassessed
Nutrition Label
Resolution chain
- 155.102.1.27
155.102.1.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 155.102.1.28
155.102.1.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 155.102.1.29
155.102.1.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 155.102.54.139
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.140
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.141
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.142
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.143
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.144
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.145
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 155.102.54.146
155.102.54.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:5373452
- 163.181.160.139
163.181.160.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 163.181.160.140
163.181.160.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 163.181.160.142
163.181.160.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 163.181.160.143
163.181.160.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 163.181.160.144
163.181.160.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:1880252
- 163.181.254.183
163.181.254.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:2925533
- 163.181.254.184
163.181.254.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:2925533
- 163.181.254.185
163.181.254.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:2925533
- 163.181.254.186
163.181.254.0/24 · Taobao - Zhejiang Taobao Network Co.,Ltd · geoname:2925533
IPv6 resolution
No AAAA record for enbon.com is recorded in WhisperGraph.
Attribution
alibaba us
ORIGIN_AS
WHOIS identity
- Registrar
- iana:420
- Registrant organisation
- domain protection services,
- Contact emails
- enbon.com@protecteddomainservices.com
Company
- Company
- Enbon Group
- Industry
- Manufacturing
- Headquarters
- Shenzhen, China
Technology
Enbon Group has been observed using 37 technologies somewhere in its estate. This is observed use, not an exposure finding. The 20 most widely adopted:
- jQuery · javascript libraries
- Open Graph · content management system
- PHP · programming languages
- Google Fonts API · font scripts
- Font Awesome · font scripts
- Google Analytics · intelligence and analytics
- Priority Hints · performance
- Nginx · web servers
- JSON-LD · frameworks and libraries
- HSTS · security
- Cloudflare · content delivery network
- Google Tag Manager · tag management
- Google Search Console · performance
- Cloudflare DNS · domain name services
- Cart Functionality · e-commerce
- Facebook · social media analytics and monitoring
- Swiper · javascript libraries
- Facebook Pixel · analytics
- cdnjs · content delivery network
- Element UI · javascript frameworks
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
DNSSEC
WhisperGraph records no DNSSEC signature for enbon.com.
DKIM signing
No DKIM signing vendor is attributed to enbon.com in WhisperGraph.
Nameservers
- austin.ns.cloudflare.com
- tori.ns.cloudflare.com
MX records
- qiye163mx01.mxmail.netease.com
- qiye163mx02.mxmail.netease.com
SPF policy
- include: spf.163.com
Threat-feed evidence
History
Related pages
Pivot from enbon.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.